Skip to main content
Glama

http_client

Send HTTP requests to any URL using GET, POST, PUT, DELETE, or HEAD methods. Useful when direct HTTP access is not available.

Instructions

Make arbitrary HTTP requests from the API hub.

Use this when you need to call a URL but don't have direct
HTTP access. Supports GET, POST, PUT, DELETE, HEAD methods.

Parameters:
    url     — The full URL to request (required).
    method  — HTTP method: 'GET' (default), 'POST', 'PUT',
              'DELETE', or 'HEAD'.
    headers — Optional JSON string of extra headers:
              '{"Authorization": "Bearer token"}'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
methodNoGET
headersNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided, so description carries full burden. It implies making requests but does not disclose potential side effects, authentication needs, rate limits, or error responses. Only mentions method support and header syntax.

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?

Very concise: single paragraph with clear purpose sentence followed by parameter list. No unnecessary words, front-loaded with key action.

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

Completeness3/5

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

Given output schema exists, return values are covered. However, lacks details on error handling, timeouts, or idempotency. Adequate for a simple HTTP client but not fully complete.

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?

Schema coverage is 0%, so description must explain parameters. It does so thoroughly: url as required full URL, method with defaults and allowed values, headers with optional JSON string and example. Adds significant meaning beyond 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?

The description clearly states the tool's purpose: making arbitrary HTTP requests from the API hub, listing supported methods. It implicitly distinguishes from sibling tools like http_headers or read_url by being a general-purpose client, but does not explicitly differentiate.

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

Usage Guidelines3/5

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

Provides a use case ('when you need to call a URL but don't have direct HTTP access'), but no exclusions or comparisons to alternatives. Lacks guidance on when not to use this tool.

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/scotia1973-bot/api-hub'

If you have feedback or need assistance with the MCP directory API, please join our Discord server