Skip to main content
Glama

CorpusIQ

by io.corpusiq
OverviewDiscussionsAdmin

Web Fetch Connector

web_fetch_connector
Read-onlyIdempotent

Grounded public-web retrieval: fetch any public web page and return its cleaned text, title, and description, each cited to the source URL and timestamped. CorpusIQ retrieves the real page content BEFORE the model reasons over it, so answers about a competitor's website, pricing page, about/careers page, or any public URL are based on fetched text — never guessed. A field the page did not contain is returned as 'unavailable'; the tool never fabricates a value. When the user asks for a visual, trend, comparison, or recap, call chart_render with the numeric values returned by this connector. If the connector result includes a verified chart_provenance token, the same authenticated user may pass it as provenance_token within 15 minutes, on any replica, and map every value to its exact source_path so chart_render preserves verified provenance. Without a valid connector receipt, chart_render labels values as unverified_model_data. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesfetch_url: Fetch a public web page and return its cleaned text plus title and description, each cited to the source URL and timesta | fetch_social_profile: Fetch grounded PUBLIC stats for a social media profile — follower count, post count, following count, display name, bio,
paramsNoAction-specific parameters. fetch_url: {url: string} | fetch_social_profile: {url: string}

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"fetch_url: Fetch a public web page and return its cleaned text plus title and description, each cited to the source URL and timesta"New value: +"fetch_url: Fetch a public web page and return its cleaned text plus title and description, each cited to the source URL and timesta | fetch_social_profile: Fetch grounded PUBLIC stats for a social media profile — follower count, post count, following count, display name, bio,"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "fetch_url"
-]New value: +[
+  "fetch_url",
+  "fetch_social_profile"
+]
    • changedInput schema / properties / params / description
      Previous value: -"Action-specific parameters. fetch_url: {url: string}"New value: +"Action-specific parameters. fetch_url: {url: string} | fetch_social_profile: {url: string}"
  2. Added

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, yet the description adds substantial behavior the annotations cannot express: missing fields return 'unavailable' rather than being fabricated, results are cited and timestamped to the source URL, the provenance_token is valid for only 15 minutes and works on any replica, and chart_render labels values unverified_model_data without a valid receipt. This is unusually rich disclosure beyond the structured fields.

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

Conciseness3/5

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

Front-loaded with the core purpose, which is good, but the description runs long and repeats itself ('never guessed' / 'never fabricates', and a lengthy accuracy contract restating the same grounding rule). Several clauses read as cross-tool output policy rather than selection/invocation guidance for this tool, and the fetch_social_profile action is never addressed in the prose.

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?

With no output schema, the description carries the return-value burden and does it well: cleaned text, title, description, per-field citation and timestamp, and the 'unavailable' sentinel. Gaps remain for a public-web fetcher — nothing about paywalled/JS-rendered pages, timeouts, size limits, or rate limits, and the second action is covered only by the schema.

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% and the enum values (fetch_url, fetch_social_profile) are already documented in the schema, so the baseline is 3. The description body explains only the fetch_url action's return semantics and says nothing extra about the url parameter's accepted form or the social-profile action, so it does not go beyond the schema.

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?

States a specific verb and resource: 'fetch any public web page and return its cleaned text, title, and description', plus the grounded-retrieval framing that distinguishes it from reasoning/guessing. It does not differentiate itself from the other *_connector siblings (it only names chart_render as a downstream consumer), so an agent still has to infer why it would choose this over, say, a site-specific connector.

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?

Gives concrete usage contexts — 'a competitor's website, pricing page, about/careers page, or any public URL' — and explicitly routes visual/trend/comparison requests to chart_render with the returned numeric values. No when-not-to-use guidance (e.g., private/authenticated pages, or which sibling connector to prefer when one exists), which keeps it short of a 5.

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

All CorpusIQ 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