Skip to main content
Glama
Sign In
compu-ai-mcp

compu-ai-mcp

by Javiervalladares1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_order

Destructive

Turn an active reservation into a confirmed order, deducting units from stock after salesperson confirmation. Supports cash, card, or installment payments.

Instructions

Turn an active reservation into a confirmed order, discounting the units from stock. This writes to the database; confirm with the salesperson before calling it.

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": {
      "reservation_code": "<reservation_code>",
      "payment_method": "<payment_method>"
    },
    "name": "create_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idNoRequired when payment_method is INSTALLMENTS.
payment_methodYes
reservation_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior5/5

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

The description explicitly states it writes to the database and discounts units from stock, aligning with the destructive annotation and making side effects clear. No hidden surprises.

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 concise sentences deliver the essential information with no redundant wording. The structure is clean and easily parseable.

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?

The description covers the core purpose and side effects, and the caution about salesperson confirmation adds important context. It does not mention return values or error scenarios, but these are not critical for a simple write operation among siblings.

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?

The description does not explain the parameters. Only plan_id has a schema description, and reservation_code and payment_method are left undocumented in both schema and description. This would force the agent to infer meanings from names alone.

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 the action: turning an active reservation into a confirmed order and reducing stock. It uses a specific verb and defines the resource and outcome unambiguously.

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?

It provides a direct usage instruction to confirm with the salesperson before calling, and implies this is a state-changing operation. This is helpful guidance, though it could be more explicit about when not to use it (e.g., if a reservation is expired).

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