Skip to main content
Glama

OmniToolCalc LLM Token & Cloud FinOps Suite

list_quantitative_calculators

List verified developer, cloud FinOps, and creator calculators with formulas and canonical URLs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_quantitative_calculators"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional keyword filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. 'List' implies a read-only operation, and the mention of verified calculators with formulas and canonical URLs gives useful context about the returned content. However, it does not describe pagination, result size, filtering behavior, or permissions, so transparency is only adequate.

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?

The description is a single, front-loaded sentence with no unnecessary wording. Every element—verb, resource categories, and included data—earns its place.

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 simple list tool with one optional parameter, no output schema, and no annotations, the description covers the core purpose and indicates what the results contain. It is nearly complete, though it could mention filtering behavior or result ordering to fully guide invocation.

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?

The schema has full description coverage for the single optional 'query' parameter ('Optional keyword filter'). The description adds no additional meaning about how the query is applied or what matching behavior to expect, so the baseline of 3 applies.

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 uses a specific verb ('List') and resource ('quantitative calculators') scoped to developer, cloud FinOps, and creator categories. It also indicates the included data (formulas and canonical URLs), making the tool's purpose clear. It does not explicitly distinguish itself from the sibling estimate_llm_token_cost, which keeps it from a 5.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It implies usage by naming calculator categories, but there are no explicit conditions, exclusions, or references to sibling 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