trademind-unified-mcp

validate_compliance

Validate trade orders against compliance rules before execution to prevent violations and ensure regulatory adherence.

Instructions

Validate trade order compliance prior to execution

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": {
      "user_id": "<user_id>",
      "symbol": "<symbol>",
      "quantity": "<quantity>"
    },
    "name": "validate_compliance"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	Yes
`user_id`	Yes
`quantity`	Yes
`workflow_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 27, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only states the purpose without mentioning important traits such as whether the tool performs side-effect-free validation, requires special permissions, or has rate limits. The behavior beyond the basic action is opaque.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no excess words, but it is so short that it sacrifices informativeness for brevity. It is appropriately concise for a simple purpose but lacks structure or additional context.

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?

Given the tool has 4 parameters, no output schema, and no annotations, the description is incomplete. It does not explain return values, error scenarios, or the validation process. The agent cannot infer how to use the tool effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, yet the description adds zero parameter-level meaning. It does not explain the purpose of optional parameters like workflow_id or the format constraints (e.g., uuid, exclusiveMinimum). The agent must rely solely on parameter names, which are insufficient.

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 uses the verb 'Validate' and provides a specific resource ('trade order compliance') with a clear temporal context ('prior to execution'). It distinguishes from sibling tools like get_portfolio_snapshot or get_allocation_breakdown which are analytical rather than pre-execution validation.

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 description does not provide any guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. The phrase 'prior to execution' weakly implies context but lacks explicit direction.

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

Deploy Server