Skip to main content
Glama

get_client_access

Read-only

The coach's role over one client: viewer type, gym role, whether they're the primary coach, and which gym capabilities they hold. Use when an action on a gym client is refused.

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": {
      "clientId": "<clientId>"
    },
    "name": "get_client_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientIdYesClient's User _id (from list_clients)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/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 value by specifying what the response conceptually contains (roles and capability flags), but says nothing about what happens for an unknown clientId, whether the data is derived/computed, or whether missing roles return empty.

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 tight sentences: the first defines the payload, the second defines the trigger. Nothing redundant, and the content is front-loaded.

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 one required parameter, no output schema, and no nested objects, the description does the main job of explaining what comes back and when to call it. A note on behavior when access is absent or the client is unknown would close the remaining gap.

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?

There is a single parameter with 100% schema description coverage, including guidance that the ID comes from list_clients. The description adds no further meaning about the parameter, so the baseline of 3 applies.

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 precisely (a coach's role over a single client) and enumerates the returned facets: viewer type, gym role, primary-coach flag, and gym capabilities. The phrase 'over one client' implicitly scopes it apart from the org-level sibling, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete triggering condition: 'Use when an action on a gym client is refused.' That is a real when-to-use signal tied to a diagnostic workflow rather than a generic 'use this to get data'. It stops short of naming alternatives (e.g., the organization-level access tool) or when not to use it.

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.