Skip to main content
Glama

BRAINIAC Crypto Tax Computation

Match internal wallet transfers

crypto-tax_transfer-match
Read-onlyIdempotent

Pair outgoing and incoming transfers between the caller's own wallets by txHash or amount/time so they are not treated as disposals. Price $0.04 USDC. POST /api/v1/crypto-tax/transfer-match. 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": {
      "ledger": "<ledger>"
    },
    "name": "crypto-tax_transfer-match"
  }
}

Input Schema

NameRequiredDescriptionDefault
ledgerYesledger, array. Required.
maxFeeRatioNomaxFeeRatio, number, from 0 to 1. Required.
windowMinutesNowindowMinutes, number, from any to 43200. Required.

Output Schema

NameRequiredDescriptionDefault
pairsNopairs. Array.
sourcesNosources. Array.
warningsNowarnings. Array.
limitationsNolimitations. Array.
unmatchedInNounmatchedIn. Array.
unmatchedOutNounmatchedOut. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description discloses commercial and operational behavior the agent could not otherwise know: a $0.04 USDC charge, the POST /api/v1/crypto-tax/transfer-match endpoint, and that an unpaid call returns x402 payment terms without executing. That payment-gate behavior is essential context for a paid tool. It stops short of saying whether matches are persisted or returned only in the response, which matters given a POST endpoint flagged readOnlyHint=true.

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?

Three short sentences with zero waste: the function and its purpose come first, then pricing and the transport endpoint, then the payment-failure behavior. Every sentence carries distinct information and nothing is repeated from the schema or annotations.

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 single-array-input computation with an output schema present, the description covers purpose, cost, endpoint, and the payment gate, so an agent can decide to call it and understands the invocation cost. It leaves unresolved whether matches are persisted and how unmatched or ambiguous entries are reported, which are the remaining gaps for an idempotent but POST-based 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?

Schema description coverage is 100%, so the baseline is 3. The description adds some meaning by explaining the matching strategy ('by txHash or amount/time'), which clarifies how txHash and the time window parameter are used together. However, it says nothing about maxFeeRatio or the windowMinutes bounds, which is precisely the kind of tuning semantics the schema's terse field notes do not convey.

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 states a specific verb and resource: pair outgoing and incoming transfers between the caller's own wallets, matched by txHash or amount/time, so they are not treated as disposals. That is concrete enough for an agent to know exactly what the tool computes. It does not name any sibling tool it should be preferred over, so it falls short of the 5 bar for explicit sibling differentiation.

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 rather than stated: the phrase 'between the caller's own wallets' signals the applicability condition (internal transfers only) and 'are not treated as disposals' implies the downstream reason to call it. There is no explicit when-not guidance, no mention of what to do when no pair is found, and no routing to alternatives such as cost-basis or missing-basis tools.

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