Skip to main content
Glama

Fetch URL

Fetch URL

chat

Fetch and extract the text content of any URL.

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": {
      "message": "<message>"
    },
    "name": "chat"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idNo
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses only that text is extracted (a partial return-shape hint), saying nothing about authentication, redirects, failures, rate limits, or size limits — and its fetch framing conflicts with the chat-shaped input schema, so the behavioral signal it does give is untrustworthy.

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?

The single sentence is front-loaded and free of filler, so structurally it is efficient. Brevity is not the problem here — the sentence is too short to carry the meaning the tool actually needs, which is under-specification rather than verbosity.

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

Completeness1/5

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

With no annotations, no output schema, 0% parameter coverage, and a description that describes a different operation than the schema implies, an agent cannot correctly invoke this tool from the definition alone. Every structured field that might have compensated (annotation hints, parameter docs, return schema) is absent.

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

Parameters1/5

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

Schema description coverage is 0% and there are two parameters ('message' required, 'chat_id' optional), yet the description never mentions either. A URL-fetching description gives no meaning to a 'message' or 'chat_id' argument, leaving both completely uninterpretable from the definition.

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

Purpose2/5

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

The sentence itself uses a specific verb and resource ('Fetch and extract the text content of any URL'), but it describes a URL-fetching utility while the tool is named 'chat' and its schema requires a 'message' plus optional 'chat_id'. An agent reading this would form a wrong model of the tool, so the purpose is not merely vague but misleading.

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

Usage Guidelines2/5

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

'Any URL' is the only scoping hint; there is no statement of when to use this versus alternatives, no preconditions, and no exclusions. No siblings are listed, so no routing guidance could be inferred either, leaving the agent with nothing actionable beyond the bare verb.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.