Skip to main content
Glama

get_organization_seat_usage

Read-only

Coach seats used vs. the plan's limit, plus billing state (NONE/TRIAL/ACTIVE/CANCELLING/PAYMENT_FAILED/ENDED), renewal date, scheduled cancel/downgrade, and coaches over the limit.

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": {
      "organizationId": "<organizationId>"
    },
    "name": "get_organization_seat_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
organizationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 the safety profile is covered. The description adds real value by disclosing the return payload (seat count vs. limit, billing state enum, renewal date, scheduled cancel/downgrade, over-limit count) in the absence of an output schema; it does not cover auth requirements or not-found behavior.

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 front-loaded sentence with no filler; the content list is compact. It is phrased as a noun phrase rather than a verb+resource statement, but nothing is wasted.

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?

For a one-parameter read-only getter the output enumeration largely carries the definition, but with no output schema and 0% parameter coverage the description should at least clarify the organizationId's meaning and behavior on an unknown or unsubscribed organization.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description never mentions the sole organizationId parameter, so no meaning is added beyond the schema's type and minLength. The parameter is guessable from the tool name, but the description does no compensating 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 a specific resource (coach seat usage vs. the plan's limit) and enumerates the exact data points returned, including the billing-state vocabulary. This distinguishes it from siblings like get_client_session_usage and list_organization_seat_tiers without naming them explicitly.

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 when-to-use guidance, no prerequisites, and no alternative named. An agent must infer from the sibling list whether this or list_organization_seat_tiers / get_organization_plans answers its question about seats or billing.

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.