TradeStaq MCP

Official

by the-staq

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

set_token

Manually configure a JWT token for authenticated API access. Intended for advanced users needing direct token control.

Instructions

Manually set a JWT token. For advanced use only.

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": {
      "token": "<token>"
    },
    "name": "set_token"
  }
}

Input Schema

Name	Required	Description	Default
`token`	Yes	JWT token from TradeStaq
`baseUrl`	No	API base URL (default: https://tradestaq.com)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 4, 2026

TDQS

C2.9/5.0

Behavior2/5

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

The description discloses that this is a manual token-setting action, but no annotations exist. It does not cover side effects (e.g., overriding existing token), authentication needs, error behavior, or whether the token is validated. For a potentially sensitive operation, more transparency is needed.

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 extremely concise—two short sentences with no extraneous words. Every part earns its place.

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

Completeness2/5

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

The description lacks any information about tool complexity, return values (no output schema), or success/failure behavior. For an advanced-use tool, more context is needed to ensure safe invocation.

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 coverage is 100%, and the description does not add any value beyond the schema's parameter descriptions. According to rules, baseline is 3 when schema covers all parameters, and the description fails to add additional meaning.

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?

The description clearly states the action ('set') and resource ('JWT token'), and the hint 'advanced use' differentiates it from simpler auth tools like authenticate or login. However, it does not explicitly distinguish from siblings that also deal with tokens.

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?

The only guidance is 'For advanced use only', which implies caution but does not specify when to use this tool versus alternatives like authenticate or login. No exclusions or prerequisites are provided.

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