Skip to main content
Glama

Plans and prices

get_plans
Read-onlyIdempotent

Bookare plans with their prices for a country (excluding VAT), limits and features, the free trial and the commission (none). The Free plan has no time limit; every new venue gets a free trial of Pro without a card.

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_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoTwo-letter ISO code, e.g. GR. Default GR.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds useful data caveats — prices exclude VAT and commission is 'none' — which prevent misreading of the returned figures. It says nothing about caching, freshness, or whether the catalog varies over time, so it adds moderate rather than rich context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler, and the returned-content list is front-loaded. However, the phrasing 'Bookare plans with their prices' and 'the commission (none)' is awkward enough to require re-reading, which costs clarity in an otherwise efficient definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 describing returns, and it does list the included fields (prices, limits, features, trial, commission). It does not indicate the shape of the response — per-plan objects, currency handling, or whether limits/features are nested — so an agent knows the content but not the structure. For a single-optional-parameter read tool this is minimally adequate.

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% and the single country parameter is fully documented there, including the ISO format and the GR default. The description mentions 'for a country' but adds no format or default detail beyond the schema. Baseline 3 is appropriate when the schema does the work.

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 names the resource (plans) and enumerates what is returned: prices per country excluding VAT, limits, features, free trial and commission. The lack of an explicit verb like 'list' or 'get' and the garbled opening ('Bookare plans') slightly blur it, but an agent can still tell this is a pricing/plan catalog lookup. Siblings are unrelated operations (create_venue, check_address), so no differentiation is needed.

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?

There is no statement of when to call this versus anything else, no prerequisites, and no exclusions. The notes about the Free plan having no time limit and new venues getting a Pro trial are domain facts about the plans, not guidance about invoking the tool. The country scoping is only visible in the schema, not in the description.

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