Skip to main content
Glama
Sign In

Wicked MCP

by io.github.WickedAPI
OverviewDiscussionsAdmin

broker_sync_transactions

Read-onlyIdempotent

[Broker Sync API] Transaction/activity history across brokerages.

Use when you want a user's transaction and activity history across brokerages. Not for current holdings (use broker_sync_positions).

Behavior: read-only. Priced via x402 (USDC on Base) or free with WICKEDAPI_API_KEY; with neither, you get HTTP 402 with the decoded price in payment_required (a price quote, not a failure).

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>"
    },
    "name": "broker_sync_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOptional. YYYY-MM-DD.
fromNoOptional. YYYY-MM-DD.
user_idYesRequired.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint false), and the description goes beyond them with non-obvious operational detail: pricing via x402/USDC, free with an API key, and that a 402 response is a price quote rather than an error. That last point prevents an agent from misclassifying a normal outcome as failure.

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?

Front-loaded one-line scope, then usage/routing, then behavior. Every sentence carries distinct load: the 402 clause in particular is the kind of detail that is expensive to rediscover at call time.

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 3-parameter read tool with no output schema, this is nearly complete: it names the resource, the alternative, and the payment/auth failure mode. The only gap is that the shape of a transaction record on success is left unspecified, so an agent cannot predict the response fields.

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%, so user_id, from, and to are already documented with date format. The description adds no parameter-level meaning (e.g., default date window or per-broker ID semantics), so the baseline of 3 applies.

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 resource (transaction/activity history) and its scope (across brokerages), and explicitly names the sibling it must not be confused with (broker_sync_positions for holdings). The bracketed API tag further disambiguates it within a large tool list.

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?

"Use when you want a user's transaction and activity history across brokerages" gives the positive trigger, and "Not for current holdings (use broker_sync_positions)" gives the exclusion plus the named alternative. Both directions of routing are covered with no inference required.

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

All Wicked MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources