Rosetta Quantum — PQC exposure

ver_archivo

Devuelve un archivo sellado completo por su ID (p.ej. 'V-0012', 'EXP-0012-001'), incluido el contenido con el que se puede recomputar su hash.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	ID del run, veredicto, receta o pre-registro

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose a meaningful behavioral trait beyond the schema: the returned file includes the content needed to recompute its hash. It omits what happens for an unknown ID, whether content is text or binary, and any size or permission constraints.

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 front-loaded sentence with the return behavior appended in a compact clause; nothing is redundant. It is slightly dense, packing scope, examples and payload contents into one statement, but no sentence 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 one-parameter read tool with no output schema and no annotations, the definition covers the essentials: what is fetched and what the payload contains. It leaves gaps around not-found behavior, content format/size, and any access requirements that an agent might need to handle results correctly.

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% and the single parameter is already documented, so the baseline is 3. The description adds real value on top by supplying concrete ID formats ('V-0012', 'EXP-0012-001'), which clarifies what the generic 'ID del run, veredicto, receta o pre-registro' schema text actually looks like.

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 ('Devuelve un archivo sellado completo por su ID') and gives concrete ID examples ('V-0012', 'EXP-0012-001'). It implicitly distinguishes itself from the status-oriented sibling 'estado_del_archivo' by emphasizing 'completo' and 'incluido el contenido', but never names an alternative explicitly.

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: fetch a sealed artifact when its full content is needed rather than just metadata. There is no explicit when-to-use/when-not-to-use guidance and no named alternative (e.g. 'estado_del_archivo' for status-only checks), so the agent must infer routing from the wording.

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

All Rosetta Quantum — PQC exposure tools Inspect

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

Need Help?