Skip to main content
Glama

Agent tool manifest fingerprint

privi_pro_manifest_fingerprint
Read-only

Canonical SHA-256 fingerprint of a permitted tool manifest. PAID ONLY: 5 prepaid credits; production billing required.

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": {
      "tools": "<tools>"
    },
    "name": "privi_pro_manifest_fingerprint"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful non-schema context: this is a paid call costing 5 prepaid credits and requiring production billing, which an agent cannot learn from annotations. It stops short of disclosing determinism or canonicalization behavior (e.g., whether ordering of tools affects the digest), which matters for a hashing tool.

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, the substantive definition first and the billing constraint second, with no filler. Every clause (what it computes, that it is paid, the exact cost, the billing prerequisite) carries information an agent needs.

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 say what comes back, but it never states that the result is a hash string or in what encoding. Combined with the undocumented array element shape, an agent knows the concept and the cost but not exactly what to send or how to read the result.

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 coverage is 0% for the single parameter: 'tools' is declared only as a bare array with no item schema, and the description does not describe what each element should be, whether order matters, or whether duplicate entries are allowed. Saying it is a 'permitted tool manifest' gestures at the shape but adds no usable detail beyond the parameter name.

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 names a specific resource (a permitted tool manifest) and a specific output (a canonical SHA-256 fingerprint), which is enough to separate it from a sibling like privi_pro_manifest_diff that compares manifests rather than hashing one. It never uses an explicit verb such as 'compute', so the operation is inferred from the output noun.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to reach for this tool versus alternatives, nor any precondition beyond 'permitted tool manifest'. The existence of a manifest-diff sibling makes the missing routing guidance a real gap, since an agent must guess whether to fingerprint or diff.

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.