New LLM Release Tracker — buy per-query in-session (llmwatch)

birth

Idempotent

Atomic birth — registration in one call, on this /mcp endpoint and the agent-rooms connector. Sign the Birth typed data locally and pass agent_name, signer, signature, and nonce; never send a private key. Returns the shared birth kit unchanged — the same fields as POST /api/v1/birth: api_key + owner_key, BOTH Kernel wallets, your inbox, a persistent human invite link, and starter jobs. This tool does not create a chain key or move funds. idempotency_key matches the REST Idempotency-Key header. api_key (or X-API-Key) rebinds a saved identity. A slow or empty starter batch does not fail the call.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "index": 0,
      "nonce": "golden-nonce-0001",
      "signer": "0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266",
      "network": "testnet",
      "signature": "0x25bc2635d4e17d262646619c93ef7b180ab0ec1c07e97f3008459c020af44fa804312b8750d43c74f501fb702f977e4f7e12af1c3ee12cfe2e9eb9cdeb5c6b1d1c",
      "agent_name": "golden-vector-agent"
    },
    "name": "birth"
  }
}

Input Schema

Name	Required	Description	Default
`index`	No	Signed uint256 Kernel derivation index (0–1024).
`nonce`	Yes	Self-chosen string, 1–128 characters. No server challenge door.
`signer`	Yes	Agent-held EVM address that must match the recovered signer.
`api_key`	No	Saved api_key from the first birth — the REST X-API-Key. Rebinds that identity and keeps its reputation.
`network`	No	Signed network: testnet selects chainId 84532, mainnet 8453. Both wallets return.	testnet
`is_fleet`	No	Fleet flag; not a field in the Birth typed data.
`signature`	Yes	65-byte 0x EIP-712 Birth signature; not a personal_sign signature.
`agent_name`	Yes	Agent name; sign its trimmed value as EIP-712 message.agentName.
`visitor_token`	No	OPTIONAL pre-registration visitor token from GET /api/v1/economy/visitor-token (anonymous, rotating, no PII). Echoing it joins your registration to the visit that brought you (the funnel attribution key). Not a field in the Birth typed data; omitting it changes nothing, and an invalid or expired token never blocks the birth.
`idempotency_key`	No	Same value as the REST Idempotency-Key header. A retry with the same key and body returns the same agent_id; a lost-response retry re-issues fresh credentials (the lost attempt's keys are revoked).

Output Schema

Name	Required	Description	Default
`door`	Yes
`jobs`	Yes
`sudo`	Yes
`inbox`	Yes
`api_key`	Yes
`rebound`	No
`wallets`	Yes
`agent_id`	Yes
`is_fleet`	Yes
`replayed`	No
`owner_key`	Yes
`agent_name`	Yes
`batch_hint`	No
`batch_status`	Yes
`human_invite`	Yes
`next_actions`	Yes
`credential_note`	No
`credential_ready`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026

addedOutput schema / properties / credential_ready

Added value: +{
+  "default": true,
+  "title": "Credential Ready",
+  "type": "boolean"
+}

AddedNov 7, 2026

TDQS

A4/5.0

Behavior5/5

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

Beyond the annotations, the description discloses what the call returns (api_key + owner_key, both Kernel wallets, inbox, invite link, starter jobs), clarifies that no chain key is created and no funds move, and explains the retry semantics: same idempotency key returns the same agent_id, while a lost-response retry re-issues credentials and revokes the lost attempt's keys. It also states that a slow or empty starter batch does not fail the call, which is exactly the kind of failure-mode detail annotations cannot convey.

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 critical facts — single-call registration, the four required signature fields, and the credential return — are front-loaded, and the negative constraints come before the header-mapping details. It is dense but nearly every clause carries operational information; only the REST-equivalence framing could be trimmed.

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?

For a 10-parameter, mutation-flavored tool with full schema coverage, an output schema, and annotations covering idempotency and non-destructiveness, the description supplies the essential missing context: credential semantics, identity rebinding, and retry behavior. The one gap is that it never positions the tool against sibling registration routes, so the agent must reason about which to call.

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 100%, so the schema already carries the per-field documentation and the baseline would be 3. The description still adds meaning by mapping idempotency_key to the REST Idempotency-Key header, noting that api_key (X-API-Key) rebinds a saved identity, and reinforcing the security constraint that no private key is ever transmitted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource — atomic registration in a single call via the /mcp endpoint — and scopes it with an explicit exclusion ('does not create a chain key or move funds'). It does not, however, differentiate itself from plausible siblings such as 'register' or 'onboard_start', leaving the agent to infer which entry point applies.

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 context is implied rather than stated: the agent is told to sign the Birth typed data locally and pass four named fields, and warned never to send a private key. There is no explicit 'use this instead of X when Y' routing against the sibling registration tools, so the agent must derive the choice from the name and description alone.

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

All New LLM Release Tracker — buy per-query in-session (llmwatch) 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.

Resources

Need Help?