Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

internet-httpStatusCode

Generates a random HTTP status code, optionally filtered by type such as success, client error, or server error, for testing and API simulations.

Instructions

Generates a random HTTP status code.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "internet-httpStatusCode"
  }
}

Input Schema

NameRequiredDescriptionDefault
typesNoA list of the HTTP status code types that should be used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It usefully reveals that generation is random (non-deterministic), which is genuine behavioral information beyond the schema. However, it says nothing about the shape of the returned value, whether a numeric code or an object is returned, or whether the call has any side effects.

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?

A single, front-loaded sentence with no filler. The purpose is stated in the first few words and nothing redundant follows.

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

Completeness3/5

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

For a simple one-parameter generator with a fully documented schema and no output schema, the description covers the core purpose. It still omits the filtering behavior of 'types' and the format of the returned status code, leaving modest gaps an agent would want closed.

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 description coverage is 100% and the single optional 'types' parameter is fully documented in the schema with an enum of status classes. The description adds no information about how filtering by type affects the generated result, so it neither compensates nor detracts. Baseline 3 applies when the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: 'Generates a random HTTP status code.' An agent can immediately tell what the tool produces and that the output is non-deterministic. It does not explicitly differentiate itself from sibling generators like internet-httpMethod or internet-color, but the resource is distinctive enough that confusion is unlikely.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives, no mention of the optional types filter, and no note about whether repeated calls yield different results. The agent must infer all usage context from the name and schema alone.

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