Skip to main content
Glama
Sign In

hamir

by app.hamir
OverviewDiscussionsAdmin

Search sources

search_sources
Read-only

Find news sites, magazines and blogs in hamir's catalogue by name, website or topic. Each result has a source_id to pass to get_source_articles.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many sources to return.
queryYesA name, website or topic, at least 3 characters.
languageNoLanguage for names and labels. Defaults to the request's Accept-Language.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already provide readOnlyHint and openWorldHint. The description adds context about the catalogue scope and the downstream use of results, which enriches understanding without contradicting annotations. It does not mention rate limits or response format details, but the annotation coverage lowers the burden.

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 concise sentences: first states the purpose and criteria, second explains the output usage. No redundant words, and the key information is front-loaded. Perfectly structured.

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 read-only search tool with no output schema, the description sufficiently covers what an agent needs: what to search, and that results contain source_id for downstream use. It could mention pagination or default behavior, but given the simple nature and annotation coverage, it is complete enough.

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 description coverage is 100%, so all parameters are documented. The description adds no extra meaning beyond what's in the schema; it merely reiterates that query matches name/website/topic. Baseline 3 is appropriate since the schema carries the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Find' and specifies the resource: 'news sites, magazines and blogs in hamir's catalogue'. It also specifies search criteria (name, website, topic) and mentions the output field (source_id), making it distinct from sibling tools like 'search' or 'list_packs'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context: to get articles from a source, you first search and obtain source_id to pass to get_source_articles. It does not explicitly contrast with siblings like 'search', but the specificity of searching for sources gives clear intent. Slight deduction for not naming alternatives directly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All hamir toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources