Skip to main content
Glama

http_post

Sends an HTTP POST request to an approved, whitelisted URL, enabling controlled data submission while enforcing default-deny policy.

Instructions

Hace un POST a una URL de la lista blanca.

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>",
      "body": "<body>"
    },
    "name": "http_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
bodyYes
approval_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 that this is an outbound POST with a whitelist constraint, which implies a side effect, but it says nothing about authentication, the meaning of approval_id (an approval workflow is strongly implied by the parameter name but never explained), retry behavior, or errors on non-whitelisted URLs.

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

Conciseness4/5

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

A single short sentence with no filler, front-loaded on the action and constraint. It is efficient but so terse that brevity shades into under-specification rather than tightness.

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

Completeness2/5

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

An output schema exists, so return values need not be described, but for a network side-effecting tool with three parameters, one of which (approval_id) appears to gate an approval workflow, the definition omits critical information. The description is not sufficient for an agent to call this safely without further assumptions.

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

Parameters2/5

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

Schema description coverage is 0%, so the schema itself gives no meaning for url, body, or approval_id, and the description only adds the whitelist constraint for url. The body's expected content type/serialization and the role of approval_id are completely undocumented in both schema and description.

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 (POST) and resource (a URL), plus a real constraint: the URL must come from a whitelist. The purpose is understandable without opening the schema, though it doesn't differentiate from the listed siblings because they are unrelated operations.

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?

No when-to-use or when-not-to-use guidance is given, and no prerequisites are stated. The single hint is the whitelist restriction on the URL, which implicitly limits usage but does not tell an agent when this tool is the right choice over alternatives.

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

Deploy Server

Other Tools