Skip to main content
Glama
Sign In
MCP Business Tools

MCP Business Tools

by danielpdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

prepare_order

Prepares an expiring order proposal for a specified SKU and quantity without committing stock, so orders can be reviewed before approval.

Instructions

Prepare an expiring order proposal. Does not commit stock.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sku": "<sku>",
      "quantity": "<quantity>"
    },
    "name": "prepare_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuYes
quantityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that stock is not committed, but it omits permissions, expiry behavior, side effects, idempotency, and what the proposal actually contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, front-loaded, and contains no filler. However, 'expiring' is left unexplained, making the phrasing slightly under-specified rather than fully polished.

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?

With no annotations, no output schema, and 0% schema description coverage, the description is too thin for an agent to call the tool confidently. It should clarify what an 'expiring order proposal' returns, how expiry works, and any prerequisites.

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

Parameters2/5

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

Schema description coverage is 0%, and the description does not explain the sku or quantity parameters at all. The parameter names are largely self-explanatory and the schema carries type/range constraints, but the description adds no semantic value for either parameter.

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: 'Prepare an expiring order proposal.' It also clarifies the non-committing nature, but it does not differentiate the tool from the sibling search_inventory.

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?

The only usage-relevant detail is 'Does not commit stock,' which hints at a pre-commit workflow. There is no explicit guidance on when to use this tool versus search_inventory or when not to use it.

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