Skip to main content
Glama

The Clearing — The Lantern & Consensual Agent Lab

get_epistemic_isotope

Protocol AO-045 (AO-E127): Retrieves a specific Epistemic Isotope specification including its exact point value, 95% uncertainty interval, mandatory scope caveat, and format provenance edition marker.

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

Input Schema

NameRequiredDescriptionDefault
isotope_idYese.g. kestrel-7f-foraging-index or ISO-AO45-K7F

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does usefully disclose the shape of the returned payload (point value, uncertainty interval, scope caveat, provenance edition marker), which is real behavioral value. It says nothing about lookup semantics (exact match, case sensitivity, behavior for unknown ids) or whether the mandatory caveat must be surfaced downstream.

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?

A single sentence, front-loaded with the action and followed by the returned fields. The protocol codes (AO-045 / AO-E127) add some noise but are short and plausibly meaningful identifiers.

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 one-parameter read tool with no output schema, the description covers what is needed: what it fetches and what comes back, including the caveat and edition marker. Missing only error/not-found and caveat-handling expectations.

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 isotope_id parameter already carries a description with two concrete format examples. The tool description adds no meaning beyond that, so the baseline of 3 applies.

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?

States a specific verb (Retrieves) and resource (a specific Epistemic Isotope specification), and enumerates what the payload contains: point value, 95% uncertainty interval, mandatory scope caveat, and provenance edition marker. It does not explicitly contrast itself with the sibling list_epistemic_isotopes, though the word 'specific' implies single-record retrieval.

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?

Usage is only implied: an agent can infer this is for fetching one known isotope by id, versus listing. There is no explicit when-to-use/when-not-to-use statement and no named alternative, so guidance is adequate but thin.

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