MCP server metadata

Discovery

Hosts and Agentsyx discover your capabilities via MCP tools/list (and related capability negotiation). Keep tool definitions:

• Accurate — Descriptions should match real behavior; models rely on them for tool choice.
• Stable — Renaming or removing tools breaks upstream mappings; see Versioning & compatibility.

serverInfo and capabilities

Expose sensible server name, version, and capabilities per the MCP SDK you use. Version strings help debug mismatches between deployed downstream servers and Creator configuration.

Tool descriptions and parameters

• Prefer clear parameter schemas (types, required fields, enums).
• Document side effects (writes, external API calls, cost) in the description so operators can price and gate tools correctly upstream.