Skip to main content
Glama

aqb_wellknown

Generates a /.well-known/agent-coin.json file using pool, token, registry, and verifier inputs to publish AQB agent settlement configuration.

Instructions

Generate your own /.well-known/agent-coin.json

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": "aqb_wellknown"
  }
}

Input Schema

NameRequiredDescriptionDefault
poolNo
tokenNo
registryNo
verifierNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says only that a file is generated and does not explain whether the file is written to disk, returned as output, requires authentication, is idempotent, or what the resulting JSON contains.

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?

It is a single short sentence, so there is no wasted wording, but it is under-specified rather than efficiently complete. The phrasing "your own" is vague and adds no operational information.

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

Completeness1/5

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

For a tool with four undocumented optional parameters, no annotations, and no output schema, the description is far too thin. It does not give an agent enough information to invoke the tool correctly or understand its output.

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?

There are four parameters (pool, token, registry, verifier) with 0% schema description coverage, and the description adds no meaning for any of them. An agent cannot tell what each parameter controls or what happens if they are omitted.

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 ("Generate") and resource ("/.well-known/agent-coin.json"), which is clearer than a bare name. It does not distinguish this from related siblings such as aqb_discover or aqb_register, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no indication of when to use this tool, when not to use it, or which sibling to prefer for related tasks. The phrase "your own" implies customization but gives no contextual guidance.

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