Skip to main content
Glama
Sign In
Wicked MCP server

Wicked MCP server

by WickedAPI
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Hybrid

broker_sync_positions

Read-onlyIdempotent

Fetch a user's real positions across all connected brokerages in one normalized schema, stamped as_of, to unify portfolio views without manual aggregation.

Instructions

[Broker Sync API] Real positions across all of a user's connected brokerages, one normalized schema, stamped as_of.

Use when you want a user's real positions across all connected brokerages in one schema. Not for cash and buying power (use broker_sync_balances).

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_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesRequired.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavioral facts: it is openWorld and priced via x402 USDC on Base, and critically that an HTTP 402 with payment_required is a price quote rather than a failure. That last detail prevents an agent from misclassifying a normal response as an error, which annotations cannot convey.

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-loads the payload in the first sentence, then labels the routing rule and the behavioral notes explicitly ('Use when', 'Not for', 'Behavior:'). Three short blocks, no filler, and the most decision-relevant content comes first.

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?

With no output schema, the description does sketch the return ('real positions ... one normalized schema, stamped as_of'), which is enough for an agent to know what comes back. It stops short of naming any position fields or the shape of the multi-brokerage aggregation, which is the only remaining gap for a single-parameter read tool.

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?

Only one parameter, and schema description coverage is 100%, so the baseline is 3. The description adds no meaning about user_id itself (e.g. that it is the broker_sync-registered user id from broker_sync_register_user), so nothing is gained 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?

States a specific resource (real broker positions across all connected brokerages) plus the key differentiator (one normalized schema, stamped as_of). It explicitly contrasts itself with broker_sync_balances, so an agent can distinguish it from the sibling without opening the schema.

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?

Gives a positive condition ('Use when you want a user's real positions across all connected brokerages in one schema') and a negative one with the named alternative ('Not for cash and buying power (use broker_sync_balances)'). That is when-to-use, when-not-to-use, and the substitute in two sentences.

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