Skip to main content
Glama
partna-mcp

partna-mcp

Official
by partna-dev

order

Records a paid customer purchase with amount, currency, and personal volume for affiliate plan and commission calculations.

Instructions

Клиент оплатил. amount — в минорных единицах (500000 = 5000.00), personalVolume — объём для расчёта плана

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": {
      "event_id": "<event_id>",
      "occurred_at": "<occurred_at>",
      "order_id": "<order_id>",
      "member_id": "<member_id>",
      "amount": "<amount>",
      "currency": "<currency>",
      "personal_volume": "<personal_volume>"
    },
    "name": "order"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYes
dry_runNo
currencyYes
event_idYes
order_idYes
member_idYes
product_idNo
occurred_atYes
retail_amountNo
personal_volumeYes
certificate_amountNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and does not disclose that this is a write/ingestion operation, whether event_id acts as an idempotency key, what side effects occur (personalVolume feeding plan calculation implies commission processing), or what dry_run does. It does add one genuinely useful behavioral fact — the minor-unit encoding of amount — but leaves the mutation profile opaque.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the highest-risk detail (unit conversion), with zero filler sentences. However, brevity here is under-specification rather than efficiency — two fragments do not constitute a structured definition, and the language differs from the English schema and sibling names.

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

Completeness1/5

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

For an 11-parameter, 7-required mutation tool with no annotations and 0% schema coverage, this definition is far from complete: required identifiers, timestamps, currency, and the dry_run flag are unexplained. The presence of an output schema excuses it from describing return values, but that does not offset the missing input and side-effect guidance.

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?

Schema description coverage is 0% across 11 parameters, so the description must compensate and it only covers two: amount (minor units, with a worked example) and personal_volume (purpose). event_id, occurred_at, currency, dry_run, product_id, retail_amount, and certificate_amount remain entirely undocumented, and the camelCase "personalVolume" does not exactly match the schema's personal_volume.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Клиент оплатил" states a fact about the customer rather than what the tool does; the agent must infer that this records an order/payment event. Nothing distinguishes it from siblings like refund, claim, or payouts, and the name "order" is a noun, not a verb+resource.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites (e.g. whether the member must exist first), and no reference to any alternative such as refund for reversals. The only implicit signal is the past-tense framing, which suggests use after payment occurs, but this is inference rather than stated guidance.

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