Skip to main content
Glama
Sign In
taap-mcp

taap-mcp

Official
by 402Protocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

resume_trading

Lifts the kill switch after a pause, reactivating trading, trigger arming, and firing for the specified trader_id.

Instructions

Lift the kill switch after pause_trading. Trading, trigger arming, and firing resume.

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": {
      "trader_id": "<trader_id>"
    },
    "name": "resume_trading"
  }
}

Input Schema

NameRequiredDescriptionDefault
trader_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the three behaviors restored (trading, trigger arming, firing), which goes beyond the name, but omits permissions, whether resuming is idempotent when already active, failure behavior, and side effects on pending triggers.

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, front-loaded sentences with zero filler; the reversal relationship comes first and the effect list second. Nothing is wasted.

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

Completeness3/5

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

For a one-parameter state-mutation tool with no annotations and no output schema, the definition covers what changes but not the identifier's semantics, error conditions, or authorization needs. Adequate but with clear gaps.

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?

The single required parameter trader_id is documented neither in the schema (0% coverage) nor in the description. The one-parameter shape is guessable, but no format, source, or scope for the identifier is given, so semantics rest entirely on convention.

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 effect ('Lift the kill switch') and names the sibling tool it reverses (pause_trading), letting an agent place it precisely among 17 siblings. The follow-on sentence enumerates exactly what resumes.

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?

Use context is clear and explicit: this is the counterpart to pause_trading, so an agent knows to call it after a pause. No when-not guidance (e.g., calling it when already running, or which trader states make it valid) is offered.

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

Deploy Server

Other Tools