Skip to main content
Glama

publish_agent_card

Publish your agent's capability card to make it discoverable by other agents. Provide capabilities, provider, and endpoint for visibility.

Instructions

Publish or update your agent's capability card for network discovery.

Makes your agent discoverable by other agents using search_agents.

IMPORTANT: This operation is idempotent — calling it again replaces
the previous card entirely. The card becomes publicly visible to all
agents on the network immediately.

Requires a registered agent identity (call register_agent first).
Use search_agents afterward to verify your card is discoverable.
Use get_my_agent_info to check your current registration status.

Side effects: creates or replaces your public capability card.
No effect on other agents' data.

Args:
    capabilities: Comma-separated capabilities. At least one required.
                  Examples: "code_review,security_audit,testing".
    provider: LLM provider powering this agent. Helps discovery filtering.
    endpoint_url: URL for receiving HTTP requests from other agents.

Returns:
    JSON with card details: capabilities list, provider, endpoint,
    and confirmation. Returns {"error": "..."} if not registered
    or on invalid input.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
capabilitiesYesComma-separated capabilities. Examples: 'code_review,security_audit,testing'. At least one required
providerNoLLM provider name. Examples: anthropic, openai, google, mistral. Optional
endpoint_urlNoHTTP endpoint for agent-to-agent interactions. Example: 'https://my-agent.example.com/api'. Optional

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description fully discloses behavior: idempotent, replaces previous card, immediate public visibility, side effects (creates/replaces own card), no effect on others, and error conditions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections (short summary, important notes, args, returns). Each sentence is informative with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema (outlined in description) and 3 parameters with full schema coverage, the description covers all necessary aspects: purpose, usage, parameters, return value, prerequisites, side effects, and verification steps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with decent descriptions, but the description adds context for each parameter (capabilities as comma-separated examples, provider for filtering, endpoint for receiving requests). Slightly improves understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Publish or update' and the resource 'capability card for network discovery'. It distinguishes from sibling tools like search_agents, get_my_agent_info, and register_agent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states prerequisites (call register_agent first), post-actions (use search_agents to verify), and alternatives (get_my_agent_info for status). Also notes idempotency and public visibility.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/agentveil-protocol/avp-sdk'

If you have feedback or need assistance with the MCP directory API, please join our Discord server