Execute HTTP requests on a stateful path for API navigation and testing. Select methods like GET, POST, or DELETE and include an optional JSON body per session.
Executes an HTTP request on the current stateful path.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No | Optional JSON payload | |
| method | No | GET | |
| session_id | No | default |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about side effects (DELETE/PUT/PATCH are available), authentication or headers, error behavior, or what is returned. 'Executes an HTTP request' implicitly signals mutation but with zero detail on destructiveness or reversibility.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no padding. It is tight, though the brevity comes at the cost of information rather than being purely efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, no annotations, and low parameter coverage, the description should compensate by explaining the session prerequisite, the source of the request path, and likely return behavior. It omits all of these for a tool that can issue destructive HTTP verbs.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 33%: 'body' and 'method' are somewhat covered, but 'session_id' is entirely undocumented in both schema and description. The description adds no parameter meaning, and critically leaves unexplained that the request target path comes from session state rather than an argument.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb ('Executes') and resource ('an HTTP request') and adds the scope qualifier 'on the current stateful path,' which hints at the stateful-session model shared with http_prompt_init/cd/configure. It does not explicitly distinguish itself from those siblings, so it stops short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no statement of when to use this tool versus the sibling init/cd/configure tools, nor any prerequisite such as 'requires a session initialized via http_prompt_init.' Usage is only inferable from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.