Skip to main content
Glama

http_get

Read-only

Fetches an absolute HTTP(S) URL via GET and returns the response body as text, so you can pull docs, JSON APIs, or reference data while working. Capped at ~100 KB with a 15s timeout.

Instructions

Fetch a URL (GET) and return the response body as text. For grabbing docs, JSON APIs, or reference data while working. Body is capped at ~100 KB; 15s timeout.

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": {
      "url": "<url>"
    },
    "name": "http_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesabsolute http(s) URL
headersNooptional request headers

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds behavior the annotations cannot convey: the body is capped at ~100 KB and the request times out at 15s, both of which affect how an agent should plan its calls. It omits how non-2xx responses are surfaced, which keeps it from a 5.

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?

Three short sentences with the core action front-loaded, followed by use cases and then the operational limits. Nothing is redundant and every sentence carries information the agent needs.

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?

For a two-parameter read tool with no output schema, the description covers purpose, use cases, return type, size cap, and timeout -- enough to call it correctly. The remaining gap is error/status-code handling, which matters for an HTTP client but is a modest omission.

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 coverage is 100%, and the schema already documents 'url' as an absolute http(s) URL and 'headers' as optional string-to-string pairs. The description adds no additional parameter semantics such as default headers or header merging behavior, so the baseline 3 applies.

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?

States a concrete verb and resource ('Fetch a URL (GET)') and the return shape ('response body as text'). That is enough for an agent to distinguish it from the get_* siblings, which all read internal project data rather than arbitrary URLs.

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 a clear usage context -- 'grabbing docs, JSON APIs, or reference data while working' -- which tells the agent when this is the right tool. It stops short of stating when not to use it or naming an alternative, but no sibling performs the same function.

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