Skip to main content
Glama
s3eidat

S3eidat Tools MCP

by s3eidat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

HTTP status codes

http_status
Read-onlyIdempotent

Look up HTTP status codes by exact code, prefix, or keywords, filter by class, and optionally include non-standard nginx/Cloudflare codes to see meanings, causes, and specs.

Instructions

Look up HTTP status codes: by exact code (e.g. 418, also non-standard ones like 499 or 524), by code prefix ("50"), or by words ("too many", "redirect post"), optionally limited to a class (1xx–5xx). Each result has the name, what it means, when to use it, common causes and the defining spec. Non-standard nginx/Cloudflare codes are only searched when "includeNonStandard" is set. Web version: https://s3eidat.github.io/http-status/

Input Schema

NameRequiredDescriptionDefault
classNoOnly this class: 1 informational, 2 success, 3 redirection, 4 client error, 5 server error.
limitNoMax results to return. Default 20.
queryNoA code ("404"), code prefix ("5", "50") or search words. Empty = all codes (filtered by class).
includeNonStandardNoAlso search non-standard codes (nginx 499, Cloudflare 52x…).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds useful behavioral detail: result fields, the fact that non-standard nginx/Cloudflare codes require includeNonStandard, and a web reference. It does not describe error behavior, but that is a minor gap for a simple lookup tool.

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?

The definition is compact and front-loaded: main lookup modes first, then return shape, then non-standard caveat. The web-version URL is not essential for invocation, which slightly reduces conciseness, but the description remains efficient overall.

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?

With no output schema, the description fully compensates by stating what each result contains (name, meaning, when to use, causes, spec). Combined with complete schema coverage and annotations covering safety, an agent has everything needed to invoke the tool correctly.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already documents all four parameters well. The description adds practical examples for the query parameter (418, 499, 524, "50", "too many", "redirect post") that clarify accepted input forms beyond the schema wording.

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 states a specific verb and resource: looking up HTTP status codes. It immediately distinguishes search modes (exact code, prefix, words, class filter) and non-standard code handling, so an agent can tell exactly what this tool does without opening the schema.

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

Usage Guidelines4/5

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

It clearly explains the available query strategies and how class filtering and non-standard inclusion work. It does not name explicit alternatives or when-not-to-use cases, but there is no obvious sibling tool for this purpose, so the context is sufficient.

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