Skip to main content
Glama
mitchallen

Synthetic Orders MCP Server

by mitchallen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MAX_BATCHNoHard cap on count. Must be ≥ 1.100
ORDER_API_URLNoWhere batches are POSTed.http://127.0.0.1:8000
REQUEST_TIMEOUT_SNoPer-request HTTP timeout.10

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
check_targetA

Report whether the configured order API is reachable, and what it holds.

preview_orderA

Generate one order and return it without sending it.

seeded samples the catalog and should be accepted; simple invents every field and should be rejected. Pass seed to reproduce an exact payload.

send_ordersA

Generate count orders and POST each one to the configured order API.

Use seeded for traffic that should be accepted and simple to drill the API's rejection path. The result reports the seed, so the same batch can be replayed by passing it back in.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
catalogThe sellable catalog rows the seeded generator draws from.
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: check_target verifies API connectivity, preview_order generates a single order without sending, and send_orders generates and sends multiple orders. There is no overlap or ambiguity between them.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (check_target, preview_order, send_orders). The naming is predictable and uniform.

Tool Count5/5

With 3 tools, the server is well-scoped for its purpose of generating and sending synthetic orders. Each tool serves a distinct function without redundancy or unnecessary bloat.

Completeness5/5

The tool set covers the essential workflow: checking the target, previewing an order, and sending orders. The ability to replay seeds in send_orders addresses the need for reproducibility, leaving no obvious gaps in the stated domain.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources