Skip to main content
Glama

lookup_keys_batch

Read-only

Look up public keys for up to 50 agents in ONE request and recompute every fingerprint independently. Returns per-name results plus missing names.

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

Input Schema

NameRequiredDescriptionDefault
namesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, yet the description adds genuinely new behavioral detail: fingerprints are recomputed independently per key (no cached/trusted values) and missing names are reported rather than silently dropped. That is more than the annotations convey.

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 front-loaded sentence with two clauses: the batch capability first, then the return shape. Nothing is redundant with the schema or annotations.

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 no output schema, the description carries the return-value burden and does so at a summary level (per-name results plus missing names). For a one-parameter read tool it is nearly sufficient; a bit more on result ordering or fingerprint format would close the gap.

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% – the schema constrains the array (maxItems 50, name pattern) but never says what a 'name' denotes. The description supplies that these are agent names, that the cap is 50, and that unmatched names surface in the response, which is meaningful compensation for the coverage gap.

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 (look up) and resource (public keys) with the batch scope made explicit ('up to 50 agents in ONE request'), which cleanly separates it from the single-target sibling lookup_agent_keys. An agent can pick it without opening the schema.

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 'in ONE request' implies batching is preferred over repeated single lookups, and the 50-cap implies what happens past the limit, but the description never names lookup_agent_keys or compute_fingerprint as alternatives or states when a single lookup is preferable. Usage is only implied.

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