Skip to main content
Glama
partna-mcp

partna-mcp

Official
by partna-dev

refund

Processes customer money-back events by reversing the related affiliate accrual, keeping commission records accurate.

Instructions

Клиенту вернули деньги: ядро откатит начисление

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>",
      "refund_id": "<refund_id>",
      "order_id": "<order_id>",
      "amount": "<amount>",
      "currency": "<currency>"
    },
    "name": "refund"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYes
dry_runNo
currencyYes
event_idYes
order_idYes
member_idNo
refund_idYes
occurred_atYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/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 it does disclose one real side effect — the core will roll back the accrual. However, it says nothing about idempotency, whether a 'dry_run' actually suppresses the rollback, permission requirements, or whether the rollback is reversible, which are critical for an 8-parameter mutation-style event.

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 a single short clause with no wasted words, so it is concise, but the cryptic past-tense phrasing and the switch to Russian against English parameter names make it harder to parse than a plain declarative sentence would be.

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

Completeness2/5

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

For a tool with 8 parameters (6 required), no annotations, and event-sourcing fields like 'event_id' and 'occurred_at', the description is far too thin. An output schema exists, so return values need not be explained, but the trigger conditions, the effect of 'dry_run', and the meaning of the event identifiers are all missing.

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

Parameters1/5

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

Schema description coverage is 0% across 8 parameters, and the description explains none of them — not 'amount', 'currency', 'occurred_at', 'member_id', or the meaningful 'dry_run' flag. With a low-coverage schema the description is expected to compensate, and it does not.

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

Purpose3/5

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

The phrase 'Клиенту вернули деньги: ядро откатит начисление' implies an event-reporting tool that records a refund so the core can roll back an accrual, but it is written as a past-tense statement of fact rather than a verb+resource declaration of what the tool does. An agent cannot tell definitively whether it performs the refund or merely reports that one occurred, and nothing distinguishes it from siblings such as 'claim' or 'payouts'.

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 preconditions, and no statement of when this should be preferred over alternatives like 'claim' or 'order'. The only hint is the implied trigger ('the client was refunded'), which the agent must infer.

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