Skip to main content
Glama

registry_positions

Read-only

Every registry's position on one result, this register included, with each one's own label preserved beside the bucket it was placed in.

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

Input Schema

NameRequiredDescriptionDefault
idYesNode id, e.g. erdos:346

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

readOnlyHint=true already establishes a safe read. The description adds some useful context about the response: it covers every registry including 'this register', and labels are preserved alongside the assigned bucket. It says nothing about ordering, missing registries, or what a 'position' record contains, so the added value is modest.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is a single sentence with no filler, but it is not front-loaded with an action and is dense with unexplained metaphors ('bucket', 'this register included'). Efficient in length, weak in readability.

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?

With one required parameter and no output schema, the description should clarify what is returned; it gestures at per-registry entries with labels and buckets but never defines them. Adequate for a simple read tool, but an agent cannot predict the response shape precisely.

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?

Schema coverage is 100% and the single id parameter is documented with a concrete example (erdos:346). The description's phrase 'one result' only loosely corroborates that the id identifies a result node, adding no format or lookup semantics beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys the resource (a result's positions across registries) but has no verb and leans on undefined jargon: 'position', 'bucket', 'this register'. An agent can guess it retrieves per-registry classifications for a given node, but it cannot state the operation confidently or tell how it differs from compare_registries.

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 when-to-use guidance, no prerequisites, and no mention of an alternative such as compare_registries, which sounds closely related. The agent must infer the selection criteria from the name alone.

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