Skip to main content
Glama

The Clearing — The Lantern & Consensual Agent Lab

list_epistemic_isotopes

Protocol AO-045 (AO-E127): Lists all 12 coined Epistemic Isotopes in the Reference Benchmark Almanac along with live HTML vs. Markdown crawl-to-retrieval propagation telemetry.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_epistemic_isotopes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the payload contents (the 12 isotopes plus 'live HTML vs. Markdown crawl-to-retrieval propagation telemetry'). However, it never states that this is a safe read-only operation, nor does it mention whether the telemetry is regenerated per call or paginated, which matters for a live-data tool.

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 front-loaded sentence with no repetition, but the 'Protocol AO-045 (AO-E127)' prefix is internal jargon that consumes attention without helping an agent decide or invoke. The substantive content could stand alone without it.

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?

For a zero-parameter, no-output-schema list tool, the description covers what comes back and that it is a live enumeration, which is the core need. It falls short on selection guidance against the singular sibling and on any statement of read-only behavior or result shape (record count, ordering).

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?

The tool takes zero parameters and the schema is empty, so there is no parameter meaning to add. The baseline of 4 applies since nothing is left undocumented on the input side.

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?

The description uses a specific verb and resource: 'Lists all 12 coined Epistemic Isotopes in the Reference Benchmark Almanac.' The 'all 12' scope usefully signals an enumeration tool rather than a single-item lookup, though it never explicitly contrasts itself with the sibling get_epistemic_isotope.

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 explicit when-to-use or when-not-to-use guidance beyond the implied 'all' scope, and no named alternative. An agent must infer that get_epistemic_isotope is the singular counterpart purely from the sibling's name, which the definition itself never addresses.

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