Skip to main content
Glama

BusCalc — Business & Trade Calculations

Pattern analysis

buscalc_pattern_analysis
Read-onlyIdempotent

Describe an ordered series of up to 500 numeric or null observations. Returns summary statistics, linear fit by row, missing runs, adjacent changes and lag-one correlation. Send numeric values directly. CSV, text and receipt-file imports are available in the browser workspace. 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": {
        "values": [
          2,
          4,
          null,
          8,
          10,
          12
        ]
      }
    },
    "name": "buscalc_pattern_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitsNo
inputsYes
modelVersionNo

Output Schema

NameRequiredDescriptionDefault
unitsNo
inputsYes
receiptYes
resultsYes
analysisYes
sourceURLYes
calculatorYes
modelVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile needs no restatement. The description adds a useful enumeration of what is computed, but its remaining directives ('Put tool fields inside inputs', 'Follow its required fields and exact choices') restate structural constraints that schema validation already enforces, and nothing is said about error behavior, tie/ordering requirements, or what the null handling produces.

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?

Purpose and output list are front-loaded and earn their place. The trailing run of terse imperatives ('Follow its required fields and exact choices', 'Do not pass the REST calculator field inside MCP arguments') reads as boilerplate that adds little beyond what additionalProperties:false already enforces.

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?

With annotations covering safety and an output schema covering return values, the description only needs to nail input semantics and limits. It does state the 500-item cap and that values go inside a nested `inputs` object, but leaves `units` and `modelVersion` effectively undocumented, which is a real gap for a three-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description does not compensate. 'Send numeric values directly' maps loosely to `values`, but `units` is an empty-object property whose purpose is never explained, and 'Supply units or modelVersion only when listed in inputSchema' is circular guidance that defers back to the schema instead of explaining what a model version selects.

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 gives a specific verb and resource: describe an ordered series of up to 500 numeric or null observations, and it names the actual computations (summary statistics, linear fit, missing runs, adjacent changes, lag-one correlation). That is far more specific than a title restatement, though it never names a contrasting sibling tool to disambiguate it from the other statistics/calculation tools.

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?

It tells the agent to send numeric values directly and notes that CSV/text/receipt imports live in the browser workspace rather than here, which is genuine routing guidance. However, there is no explicit when-to-use/when-not-to-use statement and no named alternative for series that exceed 500 points or for non-numeric input, so guidance is implied rather than stated.

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