Skip to main content
Glama
Sign In

apis-io

by io.apis
OverviewDiscussionsAdmin

register_agent

FREE, no account — register yourself in the A2A agent registry. Serve an agent card at /.well-known/agent-card.json on a host you control, then call this with its URL (or just the host). The card must be fetchable and pass the three A2A 1.0.0 hard checks: capabilities is an object, protocolVersion is present, skills is an array. 202 queues it for review; 422 says exactly which check failed. The card IS the evidence, so there is no form, no account, and nothing to wait for from us.

Input Schema

NameRequiredDescriptionDefault
roleNoOptional: whether the agent calls APIs (consumer), fronts one (provider), or both. Left out, it is inferred: a card host that serves /.well-known/api-onboarding is a provider.
contactNoOptional: an email for questions about the registration.
contextNoOptional: one sentence on why you are asking. Never used to rank; read only if a result is wrong.
card_urlYesYour agent card URL, or the host that serves it.
operatorNoOptional: who runs the agent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / context / description
      Previous value: -"Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable."New value: +"Optional: one sentence on why you are asking. Never used to rank; read only if a result is wrong."
  2. Changed1 schema field changed
    • addedInput schema / properties / role
      Added value: +{
+  "description": "Optional: whether the agent calls APIs (consumer), fronts one (provider), or both. Left out, it is inferred: a card host that serves /.well-known/api-onboarding is a provider.",
+  "enum": [
+    "consumer",
+    "provider",
+    "both"
+  ],
+  "type": "string"
+}
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description goes beyond them with outcome semantics: 202 queues for review, 422 names the failing check, and the card itself is the evidence so no form or account is required. It stops short of 5 because it never says whether repeat calls are idempotent or how long review takes.

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-loaded with the two facts that drive the decision ('FREE, no account'), then flows prerequisite to mechanics to response codes. Slightly padded by the closing reassurance about 'nothing to wait for from us', but no sentence is wasted.

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?

With no output schema, the description must carry response meaning, and it does: 202 for queued-for-review and 422 for a specific failed check. It omits what else a call can return (e.g. success/duplicate cases) and review timing, leaving a small gap for a 5-parameter registration tool.

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 100%, including the role-inference rule and the optional nature of contact/context/operator, so the schema already carries parameter meaning. The description only echoes the card_url form ('or just the host') without adding format or validation detail, which is the baseline 3 case.

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 ('register yourself in the A2A agent registry') and immediately frames the mechanism (serve a card, pass its URL). It is unmistakably distinct from read-side siblings like find_agents or get_agent_readiness, so an agent can route here without opening any schema.

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?

Gives a clear precondition chain: host an agent card at /.well-known/agent-card.json, then call with its URL or host. It does not name sibling alternatives (e.g. claim_listing) or state exclusions, so it stops short of the explicit when/when-not/alternatives bar at 5.

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

All apis-io toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources