SassyMCP

Official

Overview Schema Source Related Servers Discussions Admin

sassy_http_ping

Read-onlyIdempotent

Verify if URLs are up and measure latency with HEAD requests, returning status code and round-trip time per URL while blocking SSRF risks.

Instructions

Read-only. Health-checks one or more URLs with a HEAD request each and reports status code plus round-trip time. urls is a single comma-separated string. Each URL gets a 5-second timeout, redirects are followed, and the response lists per-URL results (status code and ms), with status blocked when SSRF validation rejects a URL or error when the request fails. SSRF protection blocks private IPs, link-local addresses, cloud metadata, and non-http(s) schemes. Use it for quick up/down and latency checks; prefer sassy_http when you need the response body or anything beyond HEAD.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`urls`	Yes

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_http_pingOutput"New value: +"sassy_http_pingDictOutput"

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?

The description discloses extensive behavioral details beyond the annotations: 5-second timeout per URL, redirect following, per-URL result structure (status code and ms), status values for blocked/error, and SSRF protections (private IPs, link-local, cloud metadata, non-http(s)). This far exceeds the readOnlyHint and idempotentHint already provided.

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 structured with the core purpose first, followed by technical details and usage guidance. Every sentence adds value—no filler—and it remains compact despite covering timeout, redirects, SSRF, and response format.

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?

For a simple health-check tool, the description is comprehensive: it covers input format, behavioral constraints, error/block handling, and selection criteria versus the sibling. Combined with the readOnlyHint and idempotentHint, nothing an agent needs 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?

The schema only defines 'urls' as a string with no description (0% coverage). The description compensates by specifying that it is 'a single comma-separated string,' which is essential for correct invocation. This fully clarifies the parameter format.

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 health-checks URLs with HEAD requests and reports status code and round-trip time. It explicitly distinguishes from the sibling sassy_http (which is for response bodies), making its purpose unambiguous and unique.

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?

It explicitly states when to use this tool ('quick up/down and latency checks') and when not to ('when you need the response body or anything beyond HEAD'), naming the alternative sassy_http. This provides clear routing guidance.

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

Deploy Server