Skip to main content
Glama
requestbin

RequestBin MCP Server

Official
by requestbin

add_mock_rule

Add a routing rule to a mock endpoint by setting method, path, status code, body, and headers. Rules are matched by priority; deploy to publish.

Instructions

Append a routing rule to a mock endpoint. Rules are matched in priority order; the first match wins. After adding rules, call deploy_mock to publish them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endpointIdYesThe mock endpoint ID (from list_mock_endpoints / create_mock_endpoint)
methodYesHTTP method to match. Use "*" to match any method.
pathYesPath to match (e.g. "/users", "/api/v1/*"). Use "*" to match any path.
statusCodeYesHTTP status code to return (100–599)
bodyNoResponse body (string; for JSON, pass a serialized JSON string)
headersNoResponse headers as a flat object (e.g. {"Content-Type": "application/json"})
priorityNoHigher priority rules are evaluated first (default 0)
Behavior3/5

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

No annotations provided; description discloses priority ordering and need to deploy, but lacks details on idempotency, error behavior, or whether addition replaces existing rules.

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 sentences, front-loaded with purpose, no redundant information.

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

Completeness4/5

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

Given no annotations or output schema, description covers core workflow (add then deploy) and ordering, but omits return value or error handling.

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 covers 100% of parameters, so baseline is 3; description adds context about priority ordering but does not enhance understanding of other parameters beyond 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?

Description specifies verb 'Append' and resource 'routing rule to a mock endpoint', clearly distinguishing from sibling tools like create_mock_endpoint and deploy_mock.

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?

Provides explicit post-usage instruction ('After adding rules, call deploy_mock to publish them') and explains matching priority, though does not contrast with alternatives for adding rules.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/requestbin/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server