Skip to main content
Glama
Sign In

Moonsox

by com.moonsox
OverviewDiscussionsAdmin

Verify a bot signed a challenge

trust_verify_signature
Read-only

Live check of a stranger: verify that signature over message (a Trust challenge message you fetched) was made by the key on the bot's Trust card.

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": {
      "botId": "<botId>",
      "message": "<message>",
      "signature": "<signature>"
    },
    "name": "trust_verify_signature"
  }
}

Input Schema

NameRequiredDescriptionDefault
botIdYes
messageYes
signatureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds that the verification is against the key on the bot's Trust card, which is useful context, but it does not describe the outcome (valid/invalid) or any failure behavior.

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?

A single well-formed sentence, front-loaded with the framing 'Live check of a stranger' and containing no filler. Efficient and readable.

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

Completeness3/5

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

There is no output schema, so the description should explain what a verification result looks like, and it does not. Combined with 0% schema coverage on three required params, the definition is adequate but leaves the return semantics 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?

Schema description coverage is 0%, so the description must carry parameter meaning. It does map 'signature' and 'message' (a Trust challenge message) to concepts and implies botId via 'the bot's Trust card,' which partially compensates, but no format or constraint details are added.

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 ('verify') and resource (a signature over a challenge message) and frames the intent as a 'live check of a stranger.' It is distinguishable from siblings by tying the check to the bot's Trust card, though it does not explicitly name the fetch sibling it depends on.

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 parenthetical 'a Trust challenge message you fetched' implies the workflow (fetch a challenge, then verify), giving implicit ordering guidance. However, it never states when to use this versus alternatives or any preconditions/exclusions explicitly.

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

All Moonsox toolsInspect
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