Skip to main content
Glama

Italian B2B Lead Scoring, Ranking & JSON Decisions

Prepare a local MS-DEC-250 order-intent template

prepare_order_intent
Read-onlyIdempotent

Return the canonical endpoint, OpenAPI, 17 required fields and an MS-DEC-250 template to fill in locally. It accepts no buyer data, creates no orders and does not authorize payments. Confirmations default to false; set them to true only after explicit consent from the authorized person. Calls update only anonymous aggregate counters in memory; submitted data is not saved.

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": {
      "product_code": "<product_code>"
    },
    "name": "prepare_order_intent"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_codeYesEntry product whose order-intent template should be prepared locally without submitting it.

Output Schema

NameRequiredDescriptionDefault
boundariesYesPermanent safety boundaries of the public MCP discovery server.
instructionsYes
product_codeYes
order_createdYes
order_openapiYes
persists_dataYes
submit_methodYes
order_endpointYes
required_fieldsYes
accepts_buyer_dataYes
idempotency_headerYes
preparation_statusYes
request_schema_refYes
local_fill_templateYes
static_order_openapiYes
checkout_url_returnedYes
provider_call_enabledYes
validation_profile_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Goes well beyond the readOnly/idempotent annotations: no buyer data consumed, no orders created, no payment authorization, and only anonymous in-memory aggregate counters updated with submitted data not saved. Minor gap: the sentence about confirmations defaulting to false refers to state that is not exposed in the input schema, which leaves the mechanism slightly unclear.

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?

Four compact sentences that front-load what is returned, then the safety envelope. Each sentence carries information, though the confirmations sentence sits oddly next to a schema containing no confirmation parameter.

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?

An output schema exists, so return values need no prose explanation, and the description covers the non-obvious guarantees (no persistence, no order creation, counters only). The only incompleteness is the dangling reference to confirmation flags that have no schema presence.

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 coverage is 100% and the single product_code parameter is already fully documented with a const of MS-DEC-250. The description's "Entry product" phrasing adds only marginal meaning beyond the schema, so the baseline 3 applies.

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?

Specific verb ("Return"/"prepare") plus concrete resource (canonical endpoint, OpenAPI, 17 required fields, MS-DEC-250 template) scoped to local fill-in. The statement that it creates no orders and accepts no buyer data makes it functionally distinguishable from any order-placement or buyer-fit sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes clear this is a local preparation step ("to fill in locally", "without submitting it"), which implies when to use it, and gives a consent rule for confirmations. It does not, however, name or contrast any sibling (e.g. get_purchase_requirements, check_buyer_fit) or state preconditions for calling this first.

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