Skip to main content
Glama

Search sources

search_sources
Read-only

Searches the catalogue of scam data sources by country, publisher, topic or what is measured. Give at least one of query, area or measure.

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

Input Schema

NameRequiredDescriptionDefault
areaNoA two-letter country code, or GLOBAL for sources that cover the world.
queryNoWords to find in the publisher, title, region or measure.
measureNoWhat the source measures.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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=true and openWorldHint=false, so safety and scope are covered. The description usefully adds the minimum-argument constraint absent from the schema, but says nothing about result size, ordering, pagination, or whether partial-word matching applies — meaningful gaps for a search tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler; the searchable facets are front-loaded and the constraint follows immediately. Nothing could be cut without losing information.

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 three-parameter search with full schema coverage and no output schema, the definition is adequate but thin — it never indicates what a result looks like (presumably a list of source records usable with get_source) or how matching behaves. A single sentence on the return shape would close the gap.

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 coverage is 100%, so all three parameters are already documented, and the description largely restates the same facets (country, publisher, topic, measure). Its only added semantic value is the at-least-one-argument rule, which the schema does not express since required is empty.

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 states a specific verb and resource ('searches the catalogue of scam data sources') plus the four filtering dimensions, so it is clearly distinguishable from retrieval-style siblings like get_source or get_country. It does not explicitly name those siblings, which keeps it short of a 5.

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?

'Give at least one of query, area or measure' is a real calling constraint, but there is no guidance on when to search versus fetching a source directly via get_source, nor any note on what to do with results. Usage is implied rather than explained.

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