Skip to main content
Glama

Kalkulator B2B

Średnia

average
Read-only

Średnia z kwot z wyników narzędzi — zamiast dzielenia w pamięci. Z period { from, to } (RRRR-MM, oba włącznie): suma kwot ÷ miesiące okresu, np. „ile średnio miesięcznie od tego kontrahenta”; miesiące liczy narzędzie. Z count: suma ÷ liczba, np. średnio na jeden przelew. Bez obu: średnia kilku kwot (np. miesięcy z tabeli). Kwoty podaj dokładnie tak, jak zwróciło je narzędzie.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "amounts": "<amounts>"
    },
    "name": "average"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoŚrednio na jedną: suma kwot ÷ liczba (np. operacji)
periodNoŚrednia miesięczna: suma kwot ÷ miesiące okresu, oba końce włącznie
amountsYesKwoty: jedna suma albo kilka wartości (np. miesięcy)
forecastNoKwoty to prognoza — wtedy okres może sięgać przyszłych miesięcy

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 safety is covered. The description adds real behavior beyond that: the tool itself counts months in the period, the forecast flag permits future months, and amounts must be passed verbatim rather than recalculated. It remains silent on rounding/precision of the result and on conflict resolution between period and count, which are the behaviors an agent would still have to guess.

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?

Front-loaded definition followed by one clause per mode, each carrying an example that earns its place. Slightly dense with stacked parentheticals and Polish quotes, but there is no filler 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 4-parameter tool with a nested period object and no output schema, the description covers input shape, the arithmetic of every mode, the month-counting rule and the forecast caveat well. Gaps are the unspecified return shape (a number is inferable but unstated) and the unresolved period+count precedence.

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 100% and each parameter already documents its own arithmetic, so the baseline is 3. The description does add combination-level semantics (the three mutually implied modes) that no single schema field states, but it never declares precedence when both period and count are set, so the gain over the schema is modest.

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?

States a concrete operation on a concrete input ('Średnia z kwot z wyników narzędzi') and enumerates the three calculation modes (period, count, neither) with short examples. An agent knows exactly what the tool computes; it just never names a sibling calculator it replaces, so it stops short of 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 Guidelines4/5

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

Gives explicit use cases for each mode ('ile średnio miesięcznie od tego kontrahenta', 'średnio na jeden przelew', 'średnia kilku kwot'), which is strong when-to-use guidance. It offers no when-not-to-use or statement about what happens if both period and count are supplied, leaving mode precedence implicit.

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