Skip to main content
Glama

List records

list_records
Read-onlyIdempotent

List genesis records, optionally by epoch (0 = founding cohort).

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_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
epochNoOptional filter: the epoch number (0 is the founding cohort).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / epoch / description
      Added value: +"Optional filter: the epoch number (0 is the founding cohort)."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only the domain meaning of epoch 0 as the founding cohort; it says nothing about ordering, pagination, or result size, which matters for a list operation.

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 short sentence with the resource and the key filter semantic front-loaded and zero filler. It is efficient, though the parenthetical domain note is redundant with the schema rather than earning new 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 single optional-parameter read tool with rich annotations and an output schema, the description supplies what is needed to call it correctly. The remaining gap is sibling differentiation and any hint about result ordering or volume, which are minor given the structured data available.

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 description coverage is 100% and the single epoch parameter is already documented in the schema, including the same note that 0 is the founding cohort. The description therefore repeats schema content rather than adding format or range details beyond it, so baseline 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 and resource: "List genesis records," which names both the operation and the entity type. It does not, however, distinguish itself from siblings like list_artifacts or recall, so an agent must infer the difference from the entity name alone.

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?

"optionally by epoch" implies the default is an unfiltered full listing and that filtering is the exception, which is useful implied guidance. It names no alternatives and gives no when-not-to-use conditions, leaving the agent to figure out how this differs from list_artifacts or recall.

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.