Skip to main content
Glama

DataAutomation

create_order

Order a service for your user. If your user authorized you to accept for them, pass accept {authorized: true, accepted_by: ""}: the order is accepted immediately and the response includes a Stripe payment_url. The user gets a confirmation email and can cancel within 48 hours. Without accept, DataAutomation emails the user an order form and the order is binding only after they accept 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": {
      "service": "<service>",
      "customer": "<customer>"
    },
    "name": "create_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNo
acceptNoAccept now on the user's behalf. Only when the user authorized you to place this order.
detailsNoWhat the user needs: systems, volumes, goals, deadlines.
optionsNo
serviceYes
customerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does so well: it discloses that acceptance is immediate, that a Stripe payment_url is returned, that a confirmation email goes out, that cancellation is possible for 48 hours, and that without accept the order is only binding after the user accepts. It does not describe failure modes or what happens if the customer's email is invalid, so it stops short of a 5.

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?

Three sentences with the core action front-loaded, followed by the conditional branch and the default path. The long accept clause is dense but every clause conveys a distinct behavioral fact, so there is little waste.

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

Completeness3/5

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

For a 6-parameter mutation tool with nested objects, no annotations, and no output schema, the description covers the accept workflow and its consequences thoroughly but leaves the customer object, service selection, and details parameter unexplained. An agent still needs the schema to know what to send for those fields, which is acceptable but not complete.

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 description coverage is only 33% across 6 parameters, so the description needs to compensate, and it only does so for the accept object, spelling out that authorized must be true and accepted_by is the authorizer's full name. The service enum values, customer fields, details, agent, and options parameters get no explanation beyond the schema itself.

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 opens with a concrete verb and object, 'Order a service for your user', which immediately distinguishes this create action from the read-oriented siblings (get_order_status, get_quote, list_services). It never names those siblings, but the create-versus-read split is unmistakable from the wording alone.

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 clearly lays out two modes of use, 'If your user authorized you to accept for them, pass accept...' versus 'Without accept, DataAutomation emails the user an order form,' so the agent knows which path to take based on the authorization state. It lacks an explicit 'do not call this before get_quote' or similar prerequisite, which keeps it just short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources