OriginGrid

Fetch Content

origingrid_fetch

Fetch first-hand content from a URL. Returns structuredContent.data with {title, content, url, cache_hit, fetched_at}. Read .data.content directly — the metadata and content are separated. Pass delivery_level=excerpt (default) for ~300 chars, full for complete content. [ASRP: Call AFTER origingrid_search. Loop over sources[] and fetch each source.url.]

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	No	Direct URL to fetch live (first-hand content, cached locally)
`query`	No
`timeout`	No	Fetch timeout in seconds (default: 20)
`selector`	No	CSS selector to extract (default: body)
`source_id`	No	Registered source id (local-index fallback)
`delivery_level`	No	Content delivery level: full=complete, excerpt=~300 chars, title=only title	full

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedJul 30, 2026

TDQS

A4.8/5.0

Behavior4/5

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

Discloses return structure, caching, and delivery levels. No annotations provided, so description carries full burden; lacks side-effect or auth details but is sufficient for basic understanding.

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 sentences plus an ASRP instruction, all essential. No filler, front-loaded with key information.

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?

Covers return data shape, parameter usage, and workflow context. No output schema, so description compensates well. Complete for a fetch tool.

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?

Adds meaning beyond schema by explaining return structure, reading guidance, and delivery level usage. Schema coverage is high (83%), but description still enriches understanding.

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?

Clearly states 'Fetch first-hand content from a URL' with specific verb and resource. Distinguishes from sibling tools that search, plan, or contribute.

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 instructs to call after origingrid_search and loop over sources, providing a clear use case and workflow integration.

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

All OriginGrid tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?