Skip to main content
Glama

Kingdom of Kantrom

verificar_sello

Verify a Kantrom timestamp seal by id: digest, date and whether the Ed25519 signature of did:web:kantrom.com is valid.

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": {
      "id": "<id>"
    },
    "name": "verificar_sello"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does convey that this is a check operation and identifies the trust anchor (did:web:kantrom.com), but it does not state whether a network/remote lookup occurs, what happens if the id does not exist, or whether failure to validate is returned as data versus an error — all material for a signature-verification call.

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?

One efficient sentence with the verb front-loaded and zero filler. The colon-appended list of returned fields slightly blurs purpose and output into one dense clause, but nothing is wasted.

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?

For a 1-parameter read-only tool with no annotations and no output schema, the description compensates reasonably by describing the return content (digest, date, signature validity). Gaps remain around id provenance and error/not-found behavior, which an agent would need in order to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter 'id' (typed only as a number). The description repeats 'by id' but adds no meaning: it does not say where the id comes from, whether it is the seal id returned by pedir_sello, or what range/format is acceptable.

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 ('Verify') and resource ('Kantrom timestamp seal by id') and even enumerates what is returned: digest, date, and Ed25519 signature validity against did:web:kantrom.com. It is clearly distinguishable from the sibling 'pedir_sello' (which issues a seal rather than checking one), though it never names that alternative.

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 only implied: 'by id' suggests you must already hold a seal id (presumably from pedir_sello), but the description never says when to call this versus the sibling tools or what preconditions exist. No explicit when/when-not guidance is given.

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