Skip to main content
Glama

Pandex

Sources and coverage

list_sources
Read-onlyIdempotent

The sources that are loaded, per jurisdiction: what each one holds, its languages, how many documents and as of which day. With a jurisdiction: also its institutions (courts, legislators), what is held of each and what is not.

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

Input Schema

NameRequiredDescriptionDefault
jurisdictionNoOnly these jurisdictions, comma-separated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 covered. The description adds real behavioral detail beyond that: it discloses the freshness dimension ('as of which day') and, importantly, that coverage gaps are reported ('what is not'), which tells the agent this tool surfaces absence as well as presence.

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 compact sentences, front-loaded with the default behavior and then the jurisdiction variant. Some phrasing is telegraphic ('as of which day', 'what is not'), which trades polish for density but stays parseable.

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-optional-parameter read tool with no output schema and full annotation coverage, the description supplies enough: what each record contains, what extra appears when filtered, and that negative coverage is reported. Minor gaps remain around result size or pagination, but nothing needed to call it correctly is missing.

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?

Schema coverage is 100% and the single parameter is already documented as a comma-separated jurisdiction filter. The description goes further by explaining the semantic effect of that parameter: including a jurisdiction changes the response shape to add institutions and their individual coverage. That is meaning not present in the schema.

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 names the resource ('sources that are loaded') and enumerates the exact per-source attributes returned: holdings, languages, document counts, and freshness date. It is clearly a catalog/coverage tool and therefore distinguishable from get_document, get_outline, get_citations, and search, though the listing verb itself is implied rather than stated.

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 implied rather than stated: an agent can infer this is the tool for discovering what sources exist and how complete they are. There is no explicit 'use this when' clause, no exclusion of alternatives, and no mention of cost or result-size considerations.

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