Skip to main content
Glama
inity13

precisioncalc-mcp

by inity13

batch_calculate

Run up to 100 calculations in a single request, reducing agent round-trips. Provide a list of tool calls with arguments; get ordered results with errors isolated per item.

Instructions

Run many calculations in one request to cut agent round-trips.

Each item is {"tool": <name>, "arguments": {...}}. Results are returned in order; a failure in one item never aborts the batch (its slot holds an error envelope). Batchable tools: calculate_metric, currency_convert, business_days, compound_growth, net_present_value, internal_rate_of_return, loan_amortization, depreciation, list_metrics.

Args: calls: List of {"tool": str, "arguments": object} items (max 100).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
callsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses important behaviors: results are returned in order, failures in individual items do not abort the batch, each failure slot holds an error envelope, and there is a maximum of 100 items. This goes beyond basic expectations and adds meaningful behavioral context.

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?

The description is moderately sized and front-loads the purpose. Each section (item format, error behavior, batchable tools) earns its place. It could be slightly more compact, but the structure is clear and logical.

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?

Given that an output schema exists, return value details need not be described. The description covers the core semantics: batch behavior, tool whitelist, ordering, partial failure handling, and item structure. It is complete enough for an agent to invoke the tool correctly.

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

Parameters4/5

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

The schema only defines 'calls' as an array of objects with no property details. The description compensates by specifying the exact item structure ({tool, arguments}) and the maximum length (100), which is essential for correct invocation. However, it does not explicitly state that the tool names must be from the provided list, though that is implied.

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?

The description uses a specific verb ('Run many calculations') and specifies the resource (calculations) and the batch context. It clearly distinguishes this tool from siblings by positioning it as a batch wrapper over the listed individual tools.

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

Usage Guidelines4/5

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

It explicitly states the goal ('to cut agent round-trips') and lists alternative individual tools that can be batched, giving clear context for when to use this tool versus calling a single tool directly. It does not explicitly state when not to use it, but the implication is strong.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/inity13/precisioncalc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server