Skip to main content
Glama

httpcat

by io.github.pipeworx-io

Get Status Cat

get_status_cat
Read-onlyIdempotent

Get a cat image representing an HTTP status code. Provide the code (e.g., 200, 404, 500). Returns the image URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
status_codeYesHTTP status code (e.g., 200, 404, 500)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
image_urlYesURL to the http.cat image for this status code
descriptionYesHuman-readable description of the status code
status_codeYesThe HTTP status code requested

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "description": {
+      "description": "Human-readable description of the status code",
+      "type": "string"
+    },
+    "image_url": {
+      "description": "URL to the http.cat image for this status code",
+      "type": "string"
+    },
+    "status_code": {
+      "description": "The HTTP status code requested",
+      "type": "number"
+    }
+  },
+  "required": [
+    "status_code",
+    "description",
+    "image_url"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "status_code": 200
+  },
+  {
+    "status_code": 404
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds a key behavioral detail: it returns an image URL. No contradiction with annotations.

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?

Two short sentences, front-loaded with the core purpose and an immediate instruction. No wasted words.

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?

The tool is simple: one parameter, output schema exists, and the description covers the essential use case. No additional context is needed for correct invocation.

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

Parameters3/5

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

Schema coverage is 100% and the status_code parameter is well-described with examples. The description repeats this information ('Provide the code (e.g., 200, 404, 500)') without adding new semantics, so the baseline 3 is appropriate.

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 uses a specific verb-resource pair ('Get a cat image representing an HTTP status code') and clearly defines the tool's scope. It is unambiguous and distinct from the unrelated sibling tools.

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?

The description gives clear context: call it when you need a cat image for an HTTP status code, and explicitly instructs to provide the code with examples. It does not mention exclusions or alternatives, but no closely related tools exist among siblings.

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

All httpcat toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation2/5

Several tools have overlapping or near-identical purposes, e.g., ask_pipeworx and ask_pipeworx_beta are explicitly described as currently equivalent, and polymarket_arbitrage, polymarket_edges, and bet_research all target prediction-market opportunities. Descriptions help somewhat, but boundaries remain fuzzy for agents.

Naming Consistency2/5

Tool names follow no consistent convention: some are verb-first (get_status_cat, remember), others are noun phrases (entity_profile, deep_research), and many use domain prefixes (ask_pipeworx, polymarket_*, pipeworx_feedback). While snake_case is maintained throughout, the structural pattern is mixed and unpredictable.

Tool Count2/5

At 33 tools, the server is well beyond the typical well-scoped range (3-15). The count is inflated by multiple overlapping meta-tools and unrelated utility groups (HTTP cats, Pipeworx research, prediction markets, memory, subscriptions), making the set feel bloated rather than focused.

Completeness2/5

The server name 'httpcat' implies HTTP status-cat functionality, but only 2 of 33 tools serve that purpose, leaving the named domain largely uncovered. As a general-purpose data server, the collection still has gaps (e.g., no direct trading, no general web search) and appears to be a random assortment of features rather than a coherent product.

Resources