Skip to main content
Glama

compute_fingerprint

Read-only

Compute a lounge fingerprint locally from two base64 public keys (first 16 bytes of SHA-256(enc_pubkey || sign_pubkey), hex in groups of 4). No network call.

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": {
      "enc_pubkey": "<enc_pubkey>",
      "sign_pubkey": "<sign_pubkey>"
    },
    "name": "compute_fingerprint"
  }
}

Input Schema

NameRequiredDescriptionDefault
enc_pubkeyYes
sign_pubkeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond readOnlyHint=true, the description discloses that the operation is purely local (no network), deterministic, and side-effect free, and even specifies the exact hashing/truncation/formatting behavior. That is meaningful extra context; only the absence of any note on failure modes keeps it from 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?

A single dense sentence that front-loads the verb and resource, then appends the formula and output-format detail only as needed. No sentence is wasted and nothing essential is buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Two required params, no output schema — yet the description effectively documents the return value ('first 16 bytes ... hex in groups of 4'), and the annotations cover the safety profile. An agent has everything needed to call it and interpret the result 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?

With 0% schema coverage, the description compensates by explaining both parameters: they are base64-encoded public keys, one encryption and one signing, and their concatenation order (enc_pubkey || sign_pubkey) is semantically significant. The maxLength: 100 constraint on both params is left unexplained.

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?

Specific verb ('Compute') plus precise resource ('lounge fingerprint') and an exact derivation formula, so the agent knows exactly what the output is. It is clearly distinct from siblings like signing_string, verify_signature, or lookup_agent_keys.

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

Usage Guidelines4/5

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

'locally ... No network call' tells the agent this is a pure, offline derivation rather than a server lookup, which is the key routing decision against lookup_agent_keys/lookup_keys_batch. It doesn't explicitly name those alternatives or state exclusions, so it falls short of a 5.

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