Skip to main content
Glama
rsi-ai-platform

rsi-search-pro-mcp

Official

web_fetch_structured

Extract specific numbers and structured data from long documents like press releases or annual reports by providing a URL and a focus. LLM-mediated extraction ensures context-aware results without hallucinations.

Instructions

Fetch a URL and extract STRUCTURED data via a focused LLM pass.

Better than plain fetch when you need SPECIFIC numbers from a long
press release / annual report / regulatory document. The extraction is
LLM-mediated so it understands context and won't hallucinate values
not on the page.

Args:
    url: The page URL.
    focus: What to extract, e.g. "CPI YoY April 2025, food inflation,
           core CPI". The LLM uses this to bias its extraction.

Returns:
    {title, dateline, summary, key_facts[], numeric_values[],
     dates[], tables_summary[]}

Requires ANTHROPIC_API_KEY env var. Without it, returns raw text only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
focusNo
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses LLM mediation, no hallucination of values, API key requirement, and return structure. Lacks error handling details.

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?

Well-structured with sections for Args and Returns. Front-loaded with main idea. Slightly verbose but informative.

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?

Covers purpose, usage context, parameter semantics, API key requirement, and return structure. Adequate given no output schema and minimal annotations.

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

Parameters4/5

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

Args section explains both parameters; focus parameter includes an example. Schema has 0% coverage, so description adds significant value.

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 it fetches a URL and extracts structured data via LLM, with specific use cases (numbers from long documents) that distinguish it from plain web_fetch.

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?

Explicitly says when to use over plain fetch (specific numbers from long documents) and mentions requirement for ANTHROPIC_API_KEY. Could be improved by stating when not to use.

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