SassyMCP

Official

Overview Schema Source Related Servers Discussions Admin

sassy_http

Destructive

Quickly call HTTP APIs with custom method, headers, body, and timeout. Get status, headers, and JSON-parsed responses while SSRF and mutating requests are blocked by default.

Instructions

Can mutate or read depending on method. GET, HEAD, and OPTIONS run freely; POST, PUT, PATCH, and DELETE require allow_mutating=True (default False). Only http and https URLs are accepted, and SSRF validation blocks private IPs, link-local addresses, and cloud metadata endpoints. headers is a JSON object string, body is a UTF-8 string, timeout_seconds defaults to 15, and redirects are followed automatically. Returns status code, headers dict, method, url, and body, which is JSON-parsed when possible and otherwise plain text truncated at 10,000 characters. Use it for quick API calls; prefer web_inspector for deep page inspection.

Input Schema

TableJSON Schema

Name	Required	Default
`url`	Yes
`body`	No
`method`	No	GET
`headers`	No
`allow_mutating`	No
`timeout_seconds`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.15.1Sep 18, 2026

addedOutput schema / additionalProperties
```
Added value: +true
```

removedOutput schema / properties

Removed value: -{
-  "result": {
-    "title": "Result",
-    "type": "string"
-  }
-}

removedOutput schema / required
```
Removed value: -[
-  "result"
-]
```

changedOutput schema / title

Previous value: -"sassy_httpOutput"New value: +"sassy_httpDictOutput"

First observedv0.1.0Jul 31, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations (readOnlyHint=false, destructiveHint=true) are general, but the description adds crucial behavioral detail: method-specific safety, SSRF protection (private IPs, link-local, cloud metadata), redirect following, JSON parsing, and 10,000-character truncation. It also clarifies the exact mutation gate, exceeding what annotations convey. No contradiction.

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?

The description is dense but every sentence adds value: safety model, URL restrictions, parameter formats, response handling, and usage guidance. It is well-ordered, front-loads the mutation gate, and avoids redundancy despite its length.

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

Completeness5/5

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

Given the tool's complexity (multiple methods, security constraints, response parsing) and the existence of an output schema, the description covers all agent-relevant aspects: allowed methods, safety checks, parameter semantics, defaults, response structure, and usage routing. Nothing needed to call it correctly is missing.

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 description coverage is 0%, yet the description compensates fully by explaining every parameter: headers as JSON object string, body as UTF-8 string, timeout_seconds default 15, method default GET, allow_mutating default False, and url as the target. It adds formats, defaults, and behavior beyond the bare schema.

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?

The description clearly states the tool makes HTTP requests with read or mutate semantics depending on method, and explicitly distinguishes itself from web_inspector for deep page inspection. It names specific verbs (GET, HEAD, OPTIONS vs POST, PUT, PATCH, DELETE) and resource scope (HTTP/HTTPS URLs), leaving no ambiguity about purpose.

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

Usage Guidelines5/5

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

Explicitly states when to use ('quick API calls') and when to prefer an alternative ('prefer web_inspector for deep page inspection'). Also provides conditional usage rules: mutating methods require allow_mutating=True, and only http/https URLs are allowed. No inference needed.

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

Deploy Server