Skip to main content
Glama

publish_agent_card

Publish or update your agent's capability card to make it discoverable on the network. Other agents can find your agent using search_agents.

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?

With no annotations, the description fully discloses behavioral traits: idempotent ('calling it again replaces the previous card entirely'), visibility ('publicly visible to all agents on the network immediately'), prerequisites ('Requires a registered agent identity'), side effects ('creates or replaces your public capability card. No effect on other agents.'), and error conditions ('Returns error if not registered or on invalid input'). Meets all transparency needs.

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?

The description is appropriately concise (~10 lines) and well-structured: a one-line purpose, followed by discovery benefit, important note, prerequisites, side effects, arguments section, and return value. Every sentence adds value, and key information is front-loaded. No unnecessary repetition or 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 tool's moderate complexity (3 parameters, 1 required) and the presence of an output schema (described in Returns), the description covers all necessary context: prerequisite steps, behavioral guarantees (idempotent, public visibility), side effects, error cases, and post-use verification. It sufficiently enables an agent to decide when and how to invoke this tool correctly relative to siblings.

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

Parameters3/5

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

Schema coverage is 100%, so description adds minimal value beyond schema. The Args section largely restates schema descriptions (e.g., 'Comma-separated capabilities. At least one required. Examples: ...'). The description provides example values for capabilities and endpoint_url, which adds slight clarity, but does not introduce new semantic constraints or clarify interdependencies. Therefore, a score of 3 is appropriate (baseline for high schema coverage).

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 tool's purpose: 'Publish or update your agent's capability card for network discovery.' It specifies the verb (publish/update) and resource (capability card). It also distinguishes from sibling tools like register_agent (registration prerequisite) and search_agents (post-publication verification), making its unique role explicit.

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?

Provides explicit prerequisites: 'Requires a registered agent identity (call register_agent first).' Advises on post-use verification: 'Use search_agents afterward to verify your card is discoverable. Use get_my_agent_info to check your current registration status.' Also clarifies when not to use by implication (requires registration, idempotent so safe to repeat). No contradictory guidance.

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