Skip to main content
Glama

list_organization_seat_tiers

Read-only

The gym subscription tiers on offer: seat limit, billing mode and price per currency (smallest unit). For a gym deciding what to buy or upgrade to.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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, so safety is covered. The description adds genuine value beyond that by disclosing the shape of the returned data (seat limit, billing mode, per-currency price in smallest units), which matters because there is no output schema.

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 resource and its fields come first, followed by the decision context. There is no filler, and the currency-unit clarification is packed economically into the first 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?

With no parameters and no output schema, the description carries the burden of explaining returned data and does so for the key fields (seat limit, billing mode, price with unit note). It is nearly complete, though it does not mention ordering, sorting, or whether all tiers are always returned.

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 the baseline is 4. The description correctly implies no inputs are needed and focuses on what the call yields, avoiding any misleading parameter claims.

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 specific resource (gym subscription tiers on offer) and enumerates the fields returned: seat limit, billing mode, and price per currency. It is clearly a read/list operation on tier options, distinguishable from get_organization_seat_usage despite not naming siblings 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?

It gives a usage context ('For a gym deciding what to buy or upgrade to'), which implies the pre-purchase/upgrade decision point. However, it never states when not to use it or points to a concrete alternative such as get_organization_seat_usage or change_organization_subscription_tier, so routing is only implied.

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.