Skip to main content
Glama

update_agent

Update an existing agent's profile by modifying only the specified fields, leaving other fields unchanged. Ideal for adjusting capabilities, contact info, or other agent settings.

Instructions

Update an existing agent's profile fields. Only provided fields are changed; omitted fields remain unchanged.

Auth: any one of —

  • Bearer agent key: set AIDRESS_AGENT_KEY env var before starting the server, or call set_agent_key("") once in-session after registering

  • Ed25519 keypair: set AIDRESS_KEYPAIR_PATH (HTTP Message Signature, RFC 9421)

  • Org key: set AIDRESS_API_KEY env var (must own this agent) Per-call key parameters are intentionally absent — bearer tokens passed as tool arguments appear in conversation history and MCP protocol trace logs.

agent_id — the agent to update (cannot be changed)

Updatable fields: org_name, org_domain, contact_info, specialty, endpoint_url, protocol, accepted_terms_format, settlement_rail, capabilities, payload_schema, message_protocol, signup_help, auth_header_name, a2a_compliant, accepted_content_types, http_methods

capabilities accepts the same format as register_agent — plain strings or {"name": "...", "weight": N} dicts.

payload_schema — semantic conventions for this agent's payloads. Dict with any of: currency (e.g. "USD"), date_format (e.g. "ISO8601"), quantity_unit (e.g. "individual_items"), weight_unit (e.g. "kg"). Only these four keys are accepted; unknown keys return 422. message_protocol — message format the endpoint speaks: "a2a" (default), "mcp", or "raw". Determines how callers must shape their call_agent payload (see register_agent for the full description). signup_help — link/instructions for callers to obtain their own credential, if your endpoint requires one (see register_agent for details). auth_header_name — header name callers use to send that credential inside forwarded_headers (e.g. "X-Api-Key", "Authorization"). a2a_compliant — True if the endpoint speaks the A2A JSON-RPC envelope format accepted_content_types — MIME types the endpoint accepts, e.g. ["application/json"]

Returns the updated trust object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYes
org_nameNo
protocolNo
specialtyNo
org_domainNo
signup_helpNo
capabilitiesNo
contact_infoNo
endpoint_urlNo
http_methodsNo
a2a_compliantNo
payload_schemaNo
settlement_railNo
auth_header_nameNo
message_protocolNo
accepted_terms_formatNo
accepted_content_typesNo
Behavior5/5

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

With no annotations, the description fully carries the burden of behavioral disclosure. It explains the partial update behavior, authentication options, field-specific constraints (e.g., capabilities format, payload_schema only accepting four keys, message_protocol options), and confirms the return value. No contradictions.

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?

The description is lengthy but well-structured with sections, bullet points, and clear paragraphs. Every sentence adds value. It could be slightly more concise by omitting some redundancy, but the structure aids readability for a complex tool with 17 parameters.

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

Completeness4/5

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

Given the high complexity (17 params, no output schema, no annotations), the description is comprehensive. It covers authentication, field behavior, constraints, and return value. The reliance on register_agent for some details is a minor gap, but overall it provides sufficient context for correct invocation.

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 0%, so the description must explain parameters. It does so for many complex fields (capabilities, payload_schema, message_protocol, signup_help, auth_header_name, a2a_compliant, accepted_content_types) and groups the simpler ones. It compensates reasonably, though some fields like org_name, specialty are self-explanatory from names. The description refers to register_agent for additional details, which slightly reduces completeness.

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 purpose: 'Update an existing agent's profile fields. Only provided fields are changed; omitted fields remain unchanged.' It specifies the verb 'update', the resource 'agent', and the behavior of partial updates. This distinguishes it from register_agent (creation) and other sibling tools.

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

Usage Guidelines4/5

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

The description provides detailed authentication methods and warns against passing bearer tokens as arguments. It tells users to see register_agent for full field descriptions, which hints at when to use that tool for creation. However, it does not explicitly state when NOT to use update_agent or compare it to other tools like get_agent or call_agent.

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/Aidress-ai/Aidress'

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