Skip to main content
Glama

Check a counterparty's mandate

symbolon_check_counterparty
Read-only

Checks a mandate shown by another agent: is it signed by its owner, valid now, is the owner's key published on the owner's website (level 'domain'), and has it been revoked? Returns the owner, scope, amount limit, any revocation and any problems. Read-only.

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": {
      "mandate": "<mandate>"
    },
    "name": "symbolon_check_counterparty"
  }
}

Input Schema

NameRequiredDescriptionDefault
mandateYesThe mandate object the other agent showed you

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description correctly reinforces the read-only nature while adding genuinely new detail: the four specific checks performed and the fact that problems are reported back. It does not explain how a 'domain' level verification is performed or what happens when the owner's website is unreachable, which keeps it from a 5.

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?

Dense but front-loaded: the action, the checks, and the returned fields all appear in two sentences with no filler. The comma-separated clause chain is slightly hard to parse, but every clause carries information.

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?

There is no output schema, and the description compensates by naming the return fields (owner, scope, amount limit, revocation, problems). For a single-parameter verification tool this is close to complete, though error and failure-mode behavior for the open-world lookup remain unstated.

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?

There is only one parameter and schema coverage is 100%, and the description's 'the mandate object the other agent showed you' adds provenance context that the schema's own wording also carries. Beyond that the description adds no structural guidance about the opaque mandate object, so the baseline of 3 is appropriate.

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?

States a specific verb and resource ('Checks a mandate shown by another agent') and enumerates exactly which properties are validated (signature, validity window, domain-level key publication, revocation). That is well beyond a restatement of the name. It does not distinguish itself from siblings such as symbolon_verify_proof, 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 Guidelines4/5

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

The phrase 'a mandate shown by another agent' establishes the context in which this tool applies, and the list of checks implies it is the pre-acceptance screening step. However, no explicit exclusions or pointers to alternative tools are given, so the agent must infer when verify_proof or lookup_fingerprint would be preferable.

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.