Skip to main content
Glama

get_client_group_limits

Read-only

Whether the coach can use client groups on their tier, and the max groups / members per group.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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 the safety profile is covered. The description adds useful content beyond that by disclosing that the response is a capability check containing both a boolean-style eligibility answer and numeric ceilings for groups and per-group members, which is exactly the behavioral context an agent needs. It does not cover error or entitlement edge cases, such as what happens on a tier with groups disabled.

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?

A single compact sentence with zero filler. The most decision-relevant fact (whether groups are usable on the tier) is front-loaded, and the quantitative limits follow immediately.

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 zero-parameter, read-only capability check with no output schema, the description is nearly sufficient: it tells the agent what the response conceptually contains. A slight gap remains because the exact shape of the returned fields (flag name, limit field names) is never stated and no output schema exists to fill that in.

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. No parameter semantics are needed, and the description correctly spends no words on inputs.

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 (client group limits) and specifies the two things it returns: tier eligibility and the maximum groups / members per group. This clearly separates it from sibling tools such as get_client_group, which fetch actual group data rather than capability limits. It stops short of a crisp verb-first statement of purpose, but the content is unambiguous.

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?

The description only implies when the tool should be used, namely before attempting group operations, by saying the result tells you whether the coach can use client groups on their tier. It never states when to call it explicitly, gives no prerequisite or ordering guidance, and does not name the alternative tools that perform the actual group work.

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.