Skip to main content
Glama

Kalkulator B2B

O serwerze Kalkulator B2B

kalkulator_info
Read-only

Co ten serwer liczy i czego nie wie. Wywołaj, gdy pytanie dotyczy danych konkretnej firmy (faktury, płatności, saldo) albo gdy nie wiesz, które narzędzie to policzy.

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": "kalkulator_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description adds the behavioral point that this tool also reports limitations ('czego nie wie'), which is useful. It says nothing about the shape or size of the returned guidance, so the addition is real but modest.

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?

Two short sentences: the capability statement first, then the call conditions. No restatement of the title, no filler, and the actionable trigger is front-loaded within the second sentence.

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 zero-parameter, read-only info/routing tool with no output schema, the description covers what it does and when to reach for it. It leaves only minor gaps, such as whether it should be consulted before any complex calculation or how authoritative its routing advice is.

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 tool takes zero parameters, so there is no parameter semantics to explain and the baseline is 4. The description correctly implies no inputs are needed by framing the call as a question-independent lookup.

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?

"Co ten serwer liczy i czego nie wie" states the resource (server capability/scope) and the verb-like action (disclose what is computed and what is not), which is a specific role rather than a tautology of the name kalkulator_info. It does not name individual siblings, so differentiation relies on the general 'tells you which tool to use' framing rather than explicit contrast with e.g. company_check or b2b_monthly.

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 gives two concrete trigger conditions: the question concerns a specific company's data (faktury, płatności, saldo), or the agent does not know which tool will calculate something. That is clear when-to-use guidance. It does not state when NOT to call it (e.g. 'skip if you already know the right tool'), which is why it falls short of a 5.

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