Skip to main content
Glama

Present an Agent Signup attestation

present_attestation

Show Yawplet who you are. Get an attestation from apis.io (POST https://apis.io/api/v1/kya/attest with aud=https://yawplet.com) and pass it as attestation, or send it in the APIs-IO-Attestation header of this MCP request. A key-bound attestation counts only if this MCP request is Web Bot Auth-signed with the bound key. The decision (trusted or known) is stored on the account; trusted raises the free search allowance and never changes prices or the owner's card requirement.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "present_attestation"
  }
}

Input Schema

NameRequiredDescriptionDefault
attestationNoThe kya+jwt, when a header is not convenient (the MCP tool and A2A skill send it this way).

Output Schema

NameRequiredDescriptionDefault
howNo
subNoThe KYA subject, e.g. wba:<domain>.
tierNo
agentNoThe agent registry slug on apis.io.
boundNoThe request was signed with the key the attestation is bound to.
issuerNo
recordNoThe public KYA record.
reasonsNo
unlocksNo
decisionNo
registryNo
disclosureNo
verified_atNo
verificationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / description
      Previous value: -"What this site decided about the agent behind the account, from an apis.io Know Your Agent attestation."New value: +"What this site decided about the agent behind the account, from an apis.io Agent Signup attestation."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag openWorldHint and non-idempotent, and the description goes beyond them by disclosing the persistent side effect (decision stored on the account), its limits (never changes prices or the owner's card requirement), and the key-binding/auth constraint that a key-bound attestation only counts if the MCP request is Web Bot Auth-signed with the bound key. It does not say what happens when no attestation is supplied or whether a call without one errors.

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?

Three dense sentences that front-load the action and then the acquisition path and the effect. The only waste is the playful opening clause, which conveys little an agent can act on compared with the rest.

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?

An output schema exists, so return values need not be explained, and the description covers the acquisition flow, the two transport options, the signing constraint, and the resulting account state. The remaining gap is the no-attestation case and any expected failure mode, which is minor but non-trivial for a tool with zero required parameters.

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 baseline is 3, and the description adds genuine value: it identifies the value as a kya+jwt, tells where to obtain it (POST https://apis.io/api/v1/kya/attest with aud=https://yawplet.com), and explains the header alternative for the same token. The schema itself only says the header route is available.

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 names the concrete action (obtain a kya attestation from apis.io and present it, via the attestation parameter or the APIs-IO-Attestation header) and the outcome (a trusted/known decision stored on the account). The opening line 'Show Yawplet who you are' is vague framing, but the mechanics that follow are specific enough to distinguish this from account or search siblings.

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 rather than stated: the reader can infer this is called to establish identity/trust and to raise the free search allowance. It never says when not to use it, what to do if you have no attestation, or how it relates to create_account or get_account, so an agent must infer the trigger condition.

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.

Resources