Skip to main content
Glama

BRAINIAC Portfolio Analytics

Detect potential US wash sales

portfolio-analytics_wash-sale-detect
Read-onlyIdempotent

Flag IRC §1091 wash sales in caller transactions with FIFO lots, disallowed losses and replacement basis adjustments per IRS Publication 550. Price $0.04 USDC. POST /api/v1/portfolio-analytics/wash-sale-detect. An unpaid call returns the x402 payment terms and does not run.

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": {
      "transactions": "<transactions>"
    },
    "name": "portfolio-analytics_wash-sale-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
lotMethodNolotMethod, string, one of fifo. Required.fifo
transactionsYestransactions, array. Required.
identicalGroupsNoidenticalGroups, array. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
washSalesNowashSales. Array.
limitationsNolimitations. Array.
allowedLossesNoallowedLosses. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/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 behavior: a $0.04 USDC price via x402, the exact endpoint, and the crucial fact that an unpaid call returns payment terms and does not execute. It stops short of describing output shape or how identical groups are matched, but the payment-gating disclosure is high-value context an agent cannot get from annotations.

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?

Four short sentences, front-loaded with the action and outcome, then price, then endpoint, then payment-failure semantics. No redundant restatement of the title and no filler.

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?

An output schema exists, so return values need no explanation, and the payment behavior plus the POST path cover the operational side. The remaining gap is the identicalGroups parameter, whose wash-sale grouping semantics are neither in the description nor meaningfully explained by the schema.

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%, so parameter documentation is already complete in the schema, establishing the baseline of 3. The description adds domain meaning to FIFO handling and basis adjustment but says nothing about identicalGroups (which symbols are treated as substantially identical) or how lotMethod interacts with transactions.

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 (Flag) plus a precise regulatory resource (IRC §1091 wash sales) and enumerates the concrete outputs: FIFO lot matching, disallowed losses, replacement basis adjustments. No sibling in the portfolio-analytics family does tax-lot wash-sale detection, so the tool is unmistakable from the list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the domain framing (IRS Publication 550, wash sales), so an agent can infer this is the tax-lot compliance check. However, it never states when to prefer it over sibling analytics tools or any preconditions/exclusions beyond the payment gate.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources