Skip to main content
Glama
tremendous-mcp

tremendous-mcp

by Bryan21B

Reject order

reject_order
Destructive

Rejects a PENDING APPROVAL order so its rewards are not sent; enable "Allow approvals via API" in Tremendous order approval settings first.

Instructions

Reject an order in status PENDING APPROVAL; its rewards are not sent. Needs "Allow approvals via API" in Tremendous Team settings → Order approvals, otherwise Tremendous answers 403. Use list_orders with status "PENDING APPROVAL" to find them.

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": {
      "id": "<id>"
    },
    "name": "reject_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOrder ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructive=true and readOnly=false, but the description adds real context beyond them: rewards are not sent, and a missing team-setting toggle ("Allow approvals via API") produces a 403. It does not state the resulting order state or whether rejection is reversible, which would complete the picture.

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?

Three short sentences, front-loaded with the action and precondition, then the settings prerequisite and the discovery path. No filler; every clause carries operational information.

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 one-parameter mutation with no output schema, the definition covers precondition, side effect, failure mode, and discovery path. The only gap is the post-success state of the order, which an agent might want to confirm.

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?

Only one parameter and schema coverage is 100%, so the baseline is 3. The description adds meaning by constraining which id is valid — an order currently in PENDING APPROVAL — which the schema's bare "Order ID" does not convey.

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 (reject) and resource (order) plus the exact state precondition (status PENDING APPROVAL) and the consequence (its rewards are not sent). That distinguishes it immediately from approve_order and cancel_reward.

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 when-to-use condition (order must be PENDING APPROVAL) and routes the agent to list_orders with status "PENDING APPROVAL" to locate candidates. It stops short of an explicit when-not or a direct contrast with approve_order/cancel_reward, so it is strong but not exhaustive.

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