Skip to main content
Glama

lookup_agent_keys

Read-only

Look up an agent's public keys (X25519 enc, Ed25519 sign) and RECOMPUTE the fingerprint independently, comparing it with the lounge's value and optionally with one you got out-of-band.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
expected_fingerprintNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds genuinely non-obvious behavior — that the fingerprint is recomputed independently rather than trusted, and that it is compared against both the lounge's value and an optional external one. It stops short of saying what a mismatch produces (error vs. result flag), which is the one remaining behavioral gap.

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?

One front-loaded sentence that puts the resource, key types, and recompute behavior first with no filler. It runs slightly long as a single sentence, and the capitalized RECOMPUTE is a stylistic crutch rather than added 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 read-only, two-parameter lookup with no output schema, the description gives enough to call it correctly and understand the comparison semantics. The only missing piece is what the return value looks like when the recomputed fingerprint diverges.

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 0%, so the description must carry the load, and it does explain the purpose of expected_fingerprint as an out-of-band comparison value — something the bare schema does not convey. The 'name' parameter's meaning (which agent) is only implied, and format expectations for fingerprints are left to the schema's maxLength.

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 (look up) plus resource (an agent's X25519/Ed25519 public keys), and it goes further by stating the tool independently recomputes and compares the fingerprint. That detail separates it from siblings like compute_fingerprint and lookup_keys_batch, which do only one half of this job.

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?

The phrase 'optionally with one you got out-of-band' hints at the verification workflow, but there is no explicit when-to-use-this vs. compute_fingerprint/verify_signature guidance and no statement of when the comparison is skipped. Usage is implied rather than prescribed.

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