Skip to main content
Glama

BusCalc — Business & Trade Calculations

ABI Codec

buscalc_chain_abi_codec
Read-onlyIdempotent

ABI-encode or decode static values (uint8..256, int8..256, address, bool, bytes1..32) exactly. Optional signature adds/validates the 4-byte selector. Read-only; builds no transactions. Put tool fields inside inputs. Supply units or modelVersion only when listed in inputSchema. Follow its required fields and exact choices. Do not pass the REST calculator field inside MCP arguments.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "inputs": {
        "mode": "encode",
        "types": [
          "uint32",
          "bool"
        ],
        "values": [
          "69",
          "true"
        ],
        "signature": "baz(uint32,bool)"
      }
    },
    "name": "buscalc_chain_abi_codec"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYes
modelVersionNo

Output Schema

NameRequiredDescriptionDefault
unitsNo
inputsYes
receiptYes
resultsYes
sourceURLYes
calculatorYes
modelVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / inputs / properties / values / description
      Added value: +"For exact integers outside the safe JSON number range, send a decimal string."
  2. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so 'Read-only; builds no transactions' largely restates structured data. The genuine addition is the signature behavior (adds and validates a selector) and 'exactly' signaling strict ABI encoding with no coercion, but nothing is said about failure modes for malformed types or mismatched signatures.

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

Conciseness3/5

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

The core capability is correctly front-loaded in the first two sentences, but the tail devolves into choppy imperative fragments ('Put tool fields inside inputs', 'Follow its required fields and exact choices') that mix MCP-transport boilerplate with tool semantics. Several of these sentences do not earn their place for an agent that already sees the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 four annotations cover the safety profile, lowering the bar. However, for a nested-object tool with an enum and two mutually dependent value lists, the description leaves the encode/decode workflow and type-value pairing unexplained, and its mention of a nonexistent 'units' field is a small mismatch with the actual 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 description coverage is 0%, so the description carries the burden and only partly meets it: it clarifies the nested 'inputs' container, the optional signature's role, and the supported type vocabulary. It does not explain mode semantics, the oneOf types-as-array-vs-string form, or pairing rules between types/values, and 'Supply units' refers to a field that does not exist in this schema, adding confusion rather than meaning.

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 first sentence names a specific verb pair (encode/decode) and resource (ABI static values) and enumerates the supported type families (uint8..256, int8..256, address, bool, bytes1..32), which is concrete enough for an agent to recognize the job. It also distinguishes itself from the selector-oriented sibling by noting the optional signature adds/validates the 4-byte selector, though it never names that sibling explicitly.

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 guidance is implied rather than stated: mode=encode vs decode must be inferred from the purpose sentence, and 'Optional signature adds/validates the 4-byte selector' hints at when to supply a signature but never says when to omit it. The remaining sentences ('Put tool fields inside inputs', 'Follow its required fields and exact choices') are argument-format housekeeping, not when-to-use vs alternatives guidance.

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