Skip to main content
Glama

Fetch a record's signed trust passport

unfragile_passport
Read-only

Fetch the raw Ed25519-signed trust passport JSON for a record (by record page slug, record id, or npm package). For programmatic policy checks; verify offline against the published public key.

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": {
      "slug": "<slug>"
    },
    "name": "unfragile_passport"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesRecord page slug, record id (npm:…), or package name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds genuinely new context by disclosing the return payload is raw signed JSON and that validation is expected to happen offline against a published key. It stops short of describing passport contents or any rate/auth constraints, which would be needed for 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and the resource, followed by the audience and the verification instruction. No filler, no repetition of the title, and 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?

For a one-parameter read tool with no output schema, the description tells the agent what comes back (raw signed JSON), what signing scheme is used (Ed25519), and what to do with it (verify offline against the published key). Only the shape of the passport document itself is left unspecified.

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?

With a single parameter at 100% schema description coverage, the schema already defines slug as a page slug, record id, or package name. The description restates those accepted forms in the parenthetical without adding format examples or edge-case behavior, so it neither adds nor detracts meaningfully.

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 ("Fetch") and a specific resource ("raw Ed25519-signed trust passport JSON"), plus the three accepted identifier forms. It differentiates itself implicitly from a verification path by saying "verify offline", but it never names or contrasts with siblings like unfragile_verify or unfragile_resolve.

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?

"For programmatic policy checks" gives a usage context that implies when this is appropriate, and "verify offline against the published public key" suggests the follow-up workflow. However, there is no explicit when-not-to-use guidance and no named alternative for agents who want server-side verification instead.

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.