Skip to main content
Glama

Freederia Research Catalog

list_public_records

Read-onlyIdempotent

Read one page of published RCRI previews.

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

Input Schema

NameRequiredDescriptionDefault
pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 safety is covered. The description adds one genuine behavioral fact beyond them — results are paginated one page at a time — but says nothing about page size, ordering, or what a "preview" contains.

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 front-loaded sentence with no filler or redundancy. It is arguably under-specified rather than verbose, but nothing in it is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no parameter documentation, the description should explain what a returned preview record looks like and how paging terminates. It instead leaves the return shape, page size, and total-count semantics entirely undefined, which is thin even for a one-parameter list tool.

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 description coverage is 0% for the single optional `page` parameter, so the description must carry the burden and largely fails: it implies paging but gives no default page, page size, or behavior at the boundary (the schema caps at 100000). "One page" only loosely gestures at the parameter.

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?

"Read one page of published RCRI previews" gives a specific verb (read) and resource (published RCRI previews) plus a scope limit (one page). It implicitly contrasts with the search_ and get_ siblings by being a paged listing, but it never names them and leaves the acronym RCRI unexplained.

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 guidance on when to choose this over search_public_records or get_public_record, nor any stated precondition for paging. The agent must infer that this is the bulk-listing entry point purely from the verb "Read" and the word "page".

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