Skip to main content
Glama

Freederia Research Catalog

search_public_records

Read-onlyIdempotent

Search public research by topic or keyword, with optional domain and method filters.

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": "search_public_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
limitNo
topicNo
cursorNo
domainNo
methodNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / topic
      Added value: +{
      +  "maxLength": 128,
      +  "type": "string"
      +}
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered without description help. The description adds that filtering by domain and method is optional, but says nothing about pagination behavior despite a cursor parameter, result caps, or ranking semantics — useful additions are missing but nothing contradicts the annotations.

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 sentence, front-loaded with the core action and resource, with the optional filters appended in a natural subordinate clause. There is no wasted wording, but the brevity reflects under-specification rather than disciplined editing.

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?

For a six-parameter search tool with zero schema descriptions and no output schema, the definition is thin: it omits pagination guidance (cursor/limit), the distinction between free-text 'q' and structured 'topic', and any sense of what a result contains. The annotations cover safety but not the call mechanics an agent needs.

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% across six parameters, so the description carries the explanatory burden and largely fails it. It mentions 'topic or keyword' and the 'domain' and 'method' filters, but never disambiguates the separate 'q' and 'topic' parameters, nor explains 'limit' (1-100) or 'cursor' pagination.

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 a specific verb ('Search') and resource ('public research') and indicates the primary query surface ('by topic or keyword'). An agent can distinguish this retrieval tool from the sibling 'get_public_record' (single fetch) and 'list_public_records' (unfiltered enumeration), though it never explicitly states that contrast.

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 only implied: the agent can infer this is the tool for topical/keyword lookups with optional narrowing filters. There is no explicit when-to-use vs. when-not, and no mention of when list_public_records or get_public_record would be preferable, so selection between the three siblings still requires inference.

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