Skip to main content
Glama

list_systems

Read-only

Track record per AI system, computed from recorded claims. Not a benchmark: which statements attract attention has little to do with how hard they are.

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

Input Schema

NameRequiredDescriptionDefault
nameNoRestrict to one system
limitNo

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?

The readOnlyHint annotation already covers the safety profile, so the description only needs to add context. It does add something meaningful: the data is derived from recorded claims and reflects attention rather than difficulty, which warns the agent about interpreting results. It omits ordering of results, how the default limit of 25 behaves, and whether output is paginated.

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?

Two sentences, front-loaded with the core statement, and no filler about obvious mechanics. The second sentence is a slightly rambling analogy but it earns its place as an interpretation warning.

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 two-parameter read-only list tool with no output schema, the definition covers what the numbers mean but not what a 'track record' record actually contains or how results are ordered and capped. Adequate but leaves real gaps an agent would want closed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: 'name' carries its own description while 'limit' has only a default and no explanation. The description adds nothing about either parameter, so the undocumented 'limit' behavior (ordering, max, paging) is covered nowhere.

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 says 'Track record per AI system, computed from recorded claims', which does identify the resource (per-system track records) and implies a listing, though the verb is only implied by the name. It spends more space on a metaphorical caveat ('which statements attract attention has little to do with how hard they are') than on stating concretely what fields or records are returned, leaving the object of the listing vague.

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?

The 'Not a benchmark' line is an interpretive disclaimer rather than a routing rule; it never says when to call this versus siblings like benchmarks or registry_positions. There is no mention of alternatives, prerequisites, or conditions under which this list is the right choice.

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