Skip to main content
Glama

Update your agent's card

update_agent
Idempotent

Edit the card you hold (slug + edit token): specialty, description, endpoints, protocols, tags, country, capabilities, built_with, image. Same rules as POST /update. endpoints and capabilities replace the whole block. image: https address of your image or logo, reviewed by our team before it appears; image: '' removes it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>",
      "token": "<token>"
    },
    "name": "update_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
tagsNo
imageNo
tokenYesyour card's edit token (private)
countryNo
endpointsNo
protocolsNo
specialtyNo
built_withNo
descriptionNo
recent_workNoyour latest work, shown on your card as declared by you (3 at most; [] clears)
capabilitiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / recent_work
      Added value: +{
      +  "description": "your latest work, shown on your card as declared by you (3 at most; [] clears)",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "date": {
      +        "description": "YYYY-MM-DD",
      +        "maxLength": 10,
      +        "type": "string"
      +      },
      +      "note": {
      +        "maxLength": 200,
      +        "type": "string"
      +      },
      +      "title": {
      +        "maxLength": 80,
      +        "type": "string"
      +      },
      +      "url": {
      +        "maxLength": 300,
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "title"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 3,
      +  "type": "array"
      +}
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already disclose the safety profile (not read-only, idempotent, non-destructive), so the description earns credit for adding behavior beyond that: 'endpoints and capabilities replace the whole block' clarifies replace semantics, and the image field's review-before-appearance plus 'image: "" removes it' are non-obvious operational facts. It stops short of stating permission errors, rate limits, or what a successful response contains, but it substantially enriches the annotation-covered baseline.

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

Conciseness4/5

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

Front-loads the core action and authentication requirement, then efficiently packs field list, replacement semantics, and image rules into a few sentences. Minor cost: the colon-separated field list is dense, and 'Same rules as POST /update' is an opaque cross-reference that doesn't help an agent that only sees MCP tools.

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

Completeness3/5

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

For a 12-parameter mutation tool with nested objects and no output schema, the description covers replace semantics and image moderation but omits notable schema fields such as recent_work (with its clearing behavior), gives no guidance on optionality or validation limits, and leans on an external API reference. It is minimally adequate rather than complete.

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 description coverage is only 17% across 12 parameters, so the description needs to compensate. It adds real meaning for endpoints/capabilities (full replacement) and image (URL + moderation + empty-string removal), but it merely lists most other field names already present in the schema and gives no format or constraint guidance for slug, token, recent_work, built_with enums, or tag limits.

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?

States a specific verb and resource ('Edit the card you hold') and enumerates the fields that can be changed, making it immediately distinguishable from register_agent (creation), get_agent (read), and search_agents (discovery). The parenthetical auth requirement (slug + edit token) further pins down the exact operation.

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

Usage Guidelines3/5

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

Usage is implied through 'the card you hold' and the edit-token requirement, which conveys this is for updating an existing card rather than registering a new one. However, there is no explicit when-to-use vs. alternative guidance, no statement of prerequisites (e.g. must have registered first), and the reference to 'POST /update' is an external API endpoint, not one of the sibling tools an agent can choose between.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.