Skip to main content
Glama
rsi-ai-platform

rsi-search-pro-mcp

Official

web_compare_across_sources

Cross-validate a claim by querying multiple authority domains in a single call. Returns per-domain top results and an agreement matrix to identify consensus or conflict.

Instructions

Issue THE SAME query across N authority domains in one call. Returns a per-domain top hit plus an agreement matrix.

Use to cross-validate a load-bearing number (e.g. "India CPI April 2025")
across MoSPI / RBI / IMF / press without writing N separate web_search
calls.

Args:
    claim_or_query: The claim or query to test.
    domains: Authority domains to compare (2-6 sweet spot).
    max_results_per_domain: 1-5.

Returns:
    {per_domain[], domains_covered, domains_total,
     agreement: "agree"|"partial"|"conflict"|"insufficient", summary}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
claim_or_queryYes
domainsYes
max_results_per_domainNo
Behavior5/5

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

No annotations provided, but description fully discloses behavior: it issues the same query across multiple domains, returns per-domain results and agreement matrix. No hidden side effects or unexpected actions.

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?

Concise and well-structured: one-sentence summary, usage guideline, annotated args, and return structure. No extraneous text.

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

Completeness5/5

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

Despite no output schema, the description includes a return structure. Parameter coverage is complete. Usage context is provided. No gaps given tool complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage, yet description adds detailed semantics for all 3 parameters: claim_or_query explained as the claim to test, domains explained as authority domains with sweet spot, max_results_per_domain range noted. This fully compensates for missing schema descriptions.

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?

Description clearly states the action: issuing the same query across multiple authority domains and returning per-domain top hits and an agreement matrix. It distinguishes from sibling tools like web_search by focusing on cross-validation across multiple domains.

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

Usage Guidelines5/5

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

Explicitly says when to use: to cross-validate a load-bearing number, and why: avoids writing N separate web_search calls. Provides domain count sweet spot (2-6) and parameter ranges.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rsi-ai-platform/rsi-search-pro-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server