Skip to main content
Glama

Upsert cancellation policy

upsert_cancellation_policy
Destructive

Create or update a cancellation policy with refund steps.

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": {
      "name": "<name>",
      "steps": "<steps>"
    },
    "name": "upsert_cancellation_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
stepsYes
policy_idNo
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.
deposit_on_cancelNo
handling_fee_unitNo
handling_fee_centsNo
credit_valid_monthsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write/destructive nature is covered elsewhere. Beyond that the description adds nothing: it does not say whether the steps array replaces existing tiers wholesale, whether omitted optional fields are cleared or left intact, or what permissions are needed — all significant for an upsert that overwrites tiered refund rules.

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?

A single short sentence with no padding and the resource front-loaded, so it is efficient. However, at this length the brevity becomes under-specification rather than economy, given eight parameters and an upsert semantic to explain.

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?

Placeholder.

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 only 13% (only business_id is documented), so the description should compensate and largely does not. Its phrase 'refund steps' loosely signals that the steps array encodes refund tiers, which is a small real gain over the bare nested schema, but name, policy_id, deposit_on_cancel, the handling-fee fields, and credit_valid_months are given no meaning at all.

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 set (create or update) and resource (cancellation policy) plus the central payload concept (refund steps). An agent can tell this writes a policy rather than reading one, though the description never contrasts it with list_cancellation_policies.

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 guidance on when to use this versus the listing sibling, nor on the crucial create-vs-update decision. The schema makes policy_id optional, which silently determines which mode runs, but the description never says that supplying policy_id updates and omitting it creates.

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