Skip to main content
Glama

list_organization_plans

Read-only

The gym-owned membership plans clients can buy through any of the gym's coaches.

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

Input Schema

NameRequiredDescriptionDefault
organizationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/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 elsewhere. Beyond that the description only adds domain framing about what a plan is; it says nothing about whether results are paginated, whether inactive/archived plans are included, or whether the caller must belong to the organization.

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?

It is a single short sentence with no filler, so nothing is wasted, but it is a noun fragment rather than an action statement, so it is not front-loaded with a verb telling the agent what happens. Adequate size, weak structure.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one required param, no output schema, read-only), which sets a low bar, but the one thing an agent must get right — supplying the correct organizationId and understanding the result scope — is entirely absent. The description reads as a gloss on the noun rather than a usable definition.

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?

There is one required parameter, organizationId, with 0% schema description coverage, and the description never mentions it — not what identifier form it takes, nor that it scopes results to a single gym. With a low-coverage schema the description was expected to compensate and does not.

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 identifies the specific resource with a scope qualifier: membership plans that are gym-owned and sold through the gym's coaches. That distinguishes it implicitly from list_my_plans and list_diet_plans, though the action verb ('list') is only carried by the tool name and the description itself is a bare noun phrase.

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 condition under which an agent should pick this over list_my_plans or list_diet_plans, and no mention of prerequisites such as needing an organization context or the right role. The 'buy through any of the gym's coaches' clause hints at the domain but does not route the agent.

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.