Skip to main content
Glama

Bereken de maandprijs van Taklo

taklo_prijs_berekenen
Read-only

Reken uit wat Taklo per maand kost voor een opgegeven aantal gebruikers. Geeft de opbouw erbij (bedrijfsbasis plus extra gebruikers) en vermeldt dat bedragen exclusief btw zijn. Alleen-lezen, geen persoonsgegevens nodig.

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": {
      "gebruikers": "<gebruikers>"
    },
    "name": "taklo_prijs_berekenen"
  }
}

Input Schema

NameRequiredDescriptionDefault
gebruikersYesAantal gebruikers (1 tot en met 50). De eerste gebruiker zit in de basis.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces this as non-destructive ('Alleen-lezen'). It also reveals what the response will contain (base fee plus extra users, amounts excluding VAT), which is real context beyond annotations; it does not mention currency or how rounding works.

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 with zero waste; the calculation purpose comes first, then the return composition and the VAT caveat. Nothing is buried or repeated.

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?

With no output schema, the description carries the burden of explaining the return value and does so: unit (per month), breakdown, and VAT exclusion. It omits currency and whether prices are rounded, which leaves a small gap.

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 coverage is 100%: the single parameter is fully documented (1 to 50, first user included in the base). The description adds only the notion that pricing consists of a company base plus extra users, which slightly helps interpretation but goes no further than the schema.

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?

It states a specific verb and resource: calculate Taklo's monthly cost for a given number of users. The purpose is unmistakable and cannot be confused with its siblings (callback scheduling, trial start, info, integrations), although it never says so explicitly.

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?

Usage is only implied: an agent can infer the tool answers pricing questions, and 'geen persoonsgegevens nodig' hints at a low-friction call. There is no explicit 'use this when...' and no comparison or exclusion against alternatives such as taklo_info.

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