Skip to main content
Glama

Crypto inventory pq migration map — Atom

Crypto inventory pq migration map

crypto_inventory_pq_migration_map
Read-onlyIdempotent

Submit a crypto inventory (algorithm, purpose, shelf-life per use); get a deterministic post-quantum migration map — each use classified (quantum-vulnerable, hybrid, PQ-ready, symmetric/hash not broken, unknown), mapped to its NIST PQ target family (ML-KEM / ML-DSA / SLH-DSA, hybrid first), and ordered in migration priority by shelf-life.

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

Input Schema

NameRequiredDescriptionDefault
systemNoSystem / estate whose cryptography is inventoried.
inventoryNoCrypto inventory entries: {id, surface, algorithm, purpose, shelf_life_years, owner}.

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 cover the safety profile (readOnlyHint=true, idempotentHint=true, openWorldHint=false, destructiveHint=false), and the description is consistent with them — 'submit/get' is clearly a non-mutating analysis. Beyond the annotations it adds genuinely useful behavioral facts: the analysis is deterministic, classification uses a fixed five-bucket taxonomy, NIST-family mapping always prefers hybrid, and ordering is driven by shelf-life. It stops short of covering handling of malformed or unknown algorithm entries, which is the only real gap given the closed-world annotation.

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 that moves cleanly from input to output to output structure, with zero filler. It is dense — three parenthetical/list clauses stacked with em-dashes — but every clause carries information the agent needs given there is no output schema.

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?

With only two fully-described parameters, no output schema, and annotations covering safety, the definition needs to characterize the return value itself — and it does, naming all five buckets, all three NIST families, and the ordering rule. Missing only edge-case behavior (empty inventory, unrecognized algorithms falling into 'unknown', how owner/surface affect output), which keeps it from a 5.

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 coverage is 100% with only two parameters, so the schema already documents both fields, and the description names the same per-entry fields (algorithm, purpose, shelf-life) that the schema lists. The added value is semantic: it tells the agent which of those fields actually drive the output (shelf-life drives ordering, purpose drives classification), which the schema does not. Baseline 3 is appropriate since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource on both sides of the operation ('Submit a crypto inventory ... get a deterministic post-quantum migration map') and enumerates the output precisely: classification into five named buckets, mapping to ML-KEM/ML-DSA/SLH-DSA, and priority ordering by shelf-life. An agent knows exactly what goes in and what comes out; no sibling tools exist to disambiguate against.

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 by the input/output framing ('submit an inventory, get a map'), which is enough to recognize the tool's role. However, there is no guidance on when this is preferable to other analysis approaches, no stated prerequisites (e.g. does the inventory need to be complete, what happens with partial entries), and no exclusions. The 'hybrid first' instruction is a downstream rule rather than a usage condition.

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.