Skip to main content
Glama
Sign In
CommerceWeave MCP

CommerceWeave MCP

by mysterekkk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get one order

commerce_get_order
Read-onlyIdempotent

Retrieve a normalized single order by platform ID from a specific connection; buyer personal data stays masked unless includePersonalData is set to true.

Instructions

Fetches one order by its platform id from a specific connection, normalized. Personal data is masked unless includePersonalData=true.

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": {
      "connectionId": "<connectionId>",
      "orderId": "<orderId>"
    },
    "name": "commerce_get_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdYes
connectionIdYes
includePersonalDataNoReturn buyer names, e-mails and phone numbers. Off by default; only enable when the task truly needs personal data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds genuinely new behavioral context: results are 'normalized' and personal data is masked by default, with the includePersonalData flag as the only way to unmask. It does not cover not-found behavior or the shape of a normalized order, which keeps it below 5.

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 tight sentences, front-loaded with the operation and lookup key, then the privacy default. No filler, no restatement of the tool name.

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?

With no output schema, the description is responsible for signaling what comes back, and 'normalized' plus the masking rule covers the most decision-relevant return behavior. A missing piece is failure behavior for an unknown orderId or mismatched connectionId, which an agent would need before calling in a loop.

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

Parameters4/5

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

Schema coverage is only 33% (only includePersonalData is documented inline), so the description must carry weight — and it does: 'platform id' clarifies that orderId is the external platform identifier, and 'from a specific connection' explains the connectionId scoping, which the bare maxLength:32 schema does not. It still omits id format expectations and connection-disambiguation behavior, so not a 5.

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?

States a specific verb and resource ('Fetches one order') plus its lookup key ('by its platform id from a specific connection'), which clearly separates it from the list-style sibling commerce_list_orders. It stops short of naming an alternative explicitly, but the singular-vs-list distinction is unambiguous.

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?

Usage is only implied: an agent infers it should call this when it needs a single known order rather than a listing. There is no explicit when-not guidance, no statement about what happens when the id is unknown, and no pointer to a search/find tool for the case where the order id is not yet known.

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