Skip to main content
Glama
Albenzoo

mockoon-mcp

by Albenzoo

create_route

Create an HTTP route with a single default response in a Mockoon environment. Specify the method, endpoint path, status code, and optional body and headers.

Instructions

Create a new HTTP route with a single default response. Use create_route_with_responses to add multiple responses in one call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
environmentIdYesEnvironment UUID
methodYesHTTP method
endpointYesRoute path without leading slash (e.g. users/:id)
documentationNoOptional documentation / description for the route
statusCodeNoHTTP status code
bodyNoResponse body (plain text or JSON string)
contentTypeNoContent-Type header valueapplication/json
headersNoAdditional response headers (excluding Content-Type)
Behavior3/5

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

With no annotations, the description carries full burden. It correctly indicates a creation operation but does not disclose potential side effects, error conditions, or permissions needed. It is adequate but not thorough.

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 the main purpose, and no extraneous information. Highly concise.

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

Completeness2/5

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

The tool has no output schema and does not explain return values (e.g., created route object) or potential errors. The description omits what happens upon success, leaving the agent uncertain about the result.

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?

The input schema has 100% description coverage, so the description adds minimal additional meaning beyond what the schema already provides. 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 clearly states 'Create a new HTTP route with a single default response', specifying the verb and resource, and distinguishes itself from the sibling tool create_route_with_responses.

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?

The description explicitly directs users to create_route_with_responses for adding multiple responses, providing clear guidance on when not to use this tool.

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/Albenzoo/Mockoon-mcp'

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