Skip to main content
Glama

Get pricing tiers

get_pricing_tiers
Read-onlyIdempotent

The pricing bundles: name, description, price per seat in a public cohort and per private team session (EUR, omitted when on request), included features, url.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: en, de or sr. Default en.en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restating. The description does add genuine behavioral context beyond them — prices are in EUR and the price field is omitted when pricing is on request — which prevents the agent from misreading a missing field as an error. It says nothing about whether the set of tiers is static or how the response is shaped beyond field names.

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?

A single compact sentence with zero filler, and the most decision-relevant nugget (prices in EUR, omitted when on request) is placed inline with the price field. The noun-phrase construction is terse to the point of being clipped, but nothing is wasteful.

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 no-required-parameter, closed-world read tool with a fully documented enum and no output schema, the description supplies the return-field inventory an agent needs to answer pricing questions without a follow-up call. The one real gap is not explaining how the lang parameter reshapes the returned text, which is a minor omission given the schema already documents the enum.

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 the sole parameter is a documented three-value enum with a default, so the schema carries the full burden. The description adds no meaning about what lang affects — notably it does not say whether translated fields include the bundle name and description — so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"The pricing bundles: name, description, price per seat..." describes the resource's contents but never states an action or scope, so the agent must infer "get" from the name and annotations. It is unambiguous about what data comes back, which keeps it above tautology, but it is a field inventory rather than a purpose statement.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives. Nothing tells the agent whether this is the right call for pricing questions versus pricing data living inside get_course or search_courses, so selection is left entirely to inference from the name.

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