Skip to main content
Glama
OrcaRail MCP

OrcaRail MCP

Official
by OrcaRail

prices.deactivate

Destructive

Mark a catalog price as inactive without deleting it. Stop offering a price while preserving its record; reactivate later by setting active to true.

Instructions

Deactivate a catalog price (it is marked inactive, not deleted). Reverse with prices.update active: 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": {
      "price_id": "<price_id>"
    },
    "name": "prices.deactivate"
  }
}

Input Schema

NameRequiredDescriptionDefault
price_idYesPrice ID
organization_idNoOrganization ID (falls back to --organization-id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.1
    • addedInput schema / properties / organization_id / pattern
      Added value: +"^[A-Za-z0-9_-]{1,128}$"
    • addedInput schema / properties / price_id / pattern
      Added value: +"^[A-Za-z0-9_-]{1,128}$"
  2. Changed1 schema field changedv1.2.0
    • addedInput schema / properties / organization_id / description
      Added value: +"Organization ID (falls back to --organization-id)"
  3. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true; the description adds genuine context beyond that by explaining the state change is a reversible soft-disable and naming the exact recovery call. There is mild tension with the destructive hint, but the description is clarifying scope rather than contradicting it — no downstream effects on existing subscriptions or permission requirements are mentioned.

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 short sentences with zero filler; the core behavior and its most important caveat are front-loaded, and the follow-up sentence earns its place by giving the recovery path.

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?

For a two-parameter mutation with annotations covering the safety profile and no output schema, this is nearly complete: an agent knows what happens to the record and how to undo it. The remaining gap is whether deactivation affects in-flight subscriptions or payments tied to the price.

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%, so both price_id and organization_id (including the --organization-id fallback) are already documented in the schema. The description adds no further meaning about these parameters, so the baseline of 3 applies.

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?

States a specific verb and resource ("Deactivate a catalog price") and immediately clarifies the semantics of that verb — marked inactive, not deleted — which is exactly the ambiguity an agent would otherwise have to guess at. It also implicitly separates itself from a hard-delete path and points at prices.update for the inverse operation.

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?

Gives a clear context for use (soft-disable rather than remove) and explicitly names the reversal route via prices.update with active: true, which is the alternative an agent most needs. It stops short of explicit when-not guidance, e.g. whether deactivating a price currently referenced by subscriptions is advisable.

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