Skip to main content
Glama
tremendous-mcp

tremendous-mcp

by Bryan21B

Approve order

approve_order
Destructive

Approves a PENDING APPROVAL order so Tremendous executes it and sends rewards; enable "Allow approvals via API" in Team settings and find orders with list_orders.

Instructions

Approve an order in status PENDING APPROVAL so Tremendous executes it and sends the reward(s). 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": "approve_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOrder ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description explains the real-world consequence: approval causes execution and reward delivery. It also discloses the account-level setting required for approvals via API and the 403 response when that setting is missing.

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?

The description is front-loaded with the action and status precondition, followed by the consequence, prerequisite, and discovery step. Every sentence contributes operational information without unnecessary wording.

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 destructive, open-world mutation with no output schema, the description covers the key consequences, preconditions, and discovery path. It does not describe the success response or retry/idempotency behavior, but the critical operational context is present.

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% for the single id parameter, so the schema already documents that it is an order ID. The description adds workflow guidance for finding eligible order IDs via list_orders, but it does not add format or validation details beyond the schema.

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?

The description gives a specific verb and resource: approve an order in status PENDING APPROVAL. It also states the effect, that Tremendous executes the order and sends the reward(s), which clearly separates it from list/get/reject siblings.

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

Usage Guidelines5/5

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

It states the required status for the order, gives the prerequisite Team setting, and explicitly directs the agent to use list_orders with status "PENDING APPROVAL" to find eligible orders. The 403 failure condition also tells the agent when the call will not work.

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