Skip to main content
Glama

BRAINIAC Crypto Tax Computation

Allocate network and gas fees

crypto-tax_network-fee-allocate
Read-onlyIdempotent

Assign network/gas fees to acquisition basis, disposal proceeds, expense or fee-asset disposal per caller policy. Price $0.02 USDC. POST /api/v1/crypto-tax/network-fee-allocate. 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": {
      "fees": "<fees>",
      "policy": "<policy>"
    },
    "name": "crypto-tax_network-fee-allocate"
  }
}

Input Schema

NameRequiredDescriptionDefault
feesYesfees, array. Required.
policyYespolicy, object. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
adjustmentsNoadjustments. Array.
limitationsNolimitations. Array.
feeAssetDisposalsNofeeAssetDisposals. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely new behavior: a $0.02 USDC price, the POST endpoint, and the crucial fact that an unpaid call returns x402 payment terms and does not execute. What it does not disclose is how fees that fail to match a policy branch are handled.

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

Conciseness4/5

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

Three short sentences, front-loaded with the action and its outcomes, followed by price/endpoint and the payment failure mode. Nothing is padded, though the price and endpoint repeat what transport metadata may already convey.

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 an output schema present, return values need no explanation, and the input schema fully documents the nested fees array and policy enums. The definition covers cost and payment gating, which an agent must know before calling; only edge-case behavior for unmatched fees is missing.

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% and the nested fee/policy objects are fully documented with enums, so the baseline of 3 applies. The description only restates the policy targets at a high level ('acquisition basis, disposal proceeds, expense or fee-asset disposal') without adding format or matching rules beyond the schema.

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?

States a specific verb ('Assign') and resource ('network/gas fees') plus the four allocation targets (acquisition basis, disposal proceeds, expense, fee-asset disposal), which map onto the policy outcomes. An agent can tell this is a fee-allocation step rather than a basis or PnL computation. No sibling is named, so differentiation is inferred rather than stated.

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?

'per caller policy' implies the tool is driven by the policy object, and the fee contexts (disposal, acquisition, transfer, failed_tx) hint at the situations it handles. However there is no explicit when-to-use/when-not guidance relative to the sibling tax tools, and no stated prerequisites beyond payment.

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