Agentry — The Trust Layer for the Agent Economy

claim_agent_api_agents_claim_post

Claim Agent

Developer claims ownership of an existing agent listing.

Responses:

200: Successful Response (Success Response) Content-Type: application/json

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": {
      "agent_id": "<agent_id>",
      "contact_email": "<contact_email>"
    },
    "name": "claim_agent_api_agents_claim_post"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`message`	No
`agent_id`	Yes
`contact_email`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedMar 23, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavior alone. It states the high-level action ('claims ownership') but omits details such as ownership verification, idempotency, side effects, or error conditions. The response section only mentions a generic 200 success, adding minimal value.

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

Conciseness3/5

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

The description is brief and front-loaded with the core purpose. However, the 'Responses' section is largely redundant (success is implied by HTTP) and takes space that could have clarified parameters or usage. Still, it is not bloated.

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

Completeness2/5

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

With four parameters, no annotations, and no output schema, the description is insufficient for an agent to reliably invoke the tool. It lacks context on the claim workflow, required inputs, and response interpretation, making it a minimal but incomplete spec.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain any of the four parameters. The purpose of name and message (optional) and the required agent_id and contact_email are left undefined, leaving the agent to guess their semantics.

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 function: a developer claims ownership of an existing agent listing. It uses a specific verb (claims) and resource (agent listing), distinguishing it from sibling tools like register_agent (new listing) and discover_single_agent.

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?

The description implies usage context (a developer claiming ownership) but provides no explicit guidance on when to use this tool versus alternatives like register_agent or get_agent. There are no exclusions or prerequisites stated.

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

All Agentry — The Trust Layer for the Agent Economy tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.