Italian B2B Lead List 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 a locally fillable MS-DEC-250 template. It accepts no buyer data and never creates an order.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`product_code`	Yes	Entry product whose order-intent template should be prepared locally without submitting it.

Output Schema

TableJSON Schema

Name	Required	Description
`boundaries`	Yes	Permanent safety boundaries of the public MCP discovery server.
`instructions`	Yes
`product_code`	Yes
`order_created`	Yes
`order_openapi`	Yes
`persists_data`	Yes
`submit_method`	Yes
`order_endpoint`	Yes
`required_fields`	Yes
`accepts_buyer_data`	Yes
`idempotency_header`	Yes
`preparation_status`	Yes
`request_schema_ref`	Yes
`local_fill_template`	Yes
`static_order_openapi`	Yes
`checkout_url_returned`	Yes
`provider_call_enabled`	Yes
`validation_profile_url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 21, 2026

addedOutput schema / properties / validation_profile_url

Added value: +{
+  "format": "uri",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "preparation_status",
-  "product_code",
-  "submit_method",
-  "order_endpoint",
-  "order_openapi",
-  "static_order_openapi",
-  "request_schema_ref",
-  "idempotency_header",
-  "required_fields",
-  "local_fill_template",
-  "instructions",
-  "accepts_buyer_data",
-  "persists_data",
-  "order_created",
-  "checkout_url_returned",
-  "provider_call_enabled",
-  "boundaries"
-]New value: +[
+  "preparation_status",
+  "product_code",
+  "submit_method",
+  "order_endpoint",
+  "order_openapi",
+  "static_order_openapi",
+  "request_schema_ref",
+  "validation_profile_url",
+  "idempotency_header",
+  "required_fields",
+  "local_fill_template",
+  "instructions",
+  "accepts_buyer_data",
+  "persists_data",
+  "order_created",
+  "checkout_url_returned",
+  "provider_call_enabled",
+  "boundaries"
+]

AddedJul 21, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description adds value beyond annotations (readOnlyHint, idempotentHint, destructiveHint) by stating 'It accepts no buyer data and never creates an order,' which provides key behavioral context not in annotations. No contradiction.

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 sentences, front-loaded with the most important information (what it returns), and no unnecessary words. Every sentence serves a purpose.

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

Completeness5/5

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

Given the tool's simplicity (one parameter, no nested objects, good annotations, output schema exists), the description fully covers the tool's purpose, behavior, and limitations. No gaps.

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 100% for the single parameter (product_code with const and description), so the description does not need to add parameter details. Baseline 3 is appropriate; no extra semantic value from description.

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 that it returns a canonical endpoint, OpenAPI, required fields, and a fillable template for MS-DEC-250. It uses a specific verb 'return' and resource 'MS-DEC-250 order-intent template', distinguishing it from siblings like 'check_buyer_fit' which check fit, not prepare templates.

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?

The description explicitly says 'It accepts no buyer data and never creates an order', which guides when not to use it. However, it does not explicitly state when to use it or name alternatives, leaving room for clearer context.

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

All Italian B2B Lead List Scoring, Ranking & JSON Decisions tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?