Skip to main content
Glama

get_organization_dashboard

Read-only

Organization-wide totals: clients and revenue overall, and broken down per location and per coach.

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

Input Schema

NameRequiredDescriptionDefault
coachIdNo
locationIdNo
organizationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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 contributes the result shape (overall plus per-location and per-coach breakdowns), but says nothing about permissions needed, whether the breakdowns are always present, or whether any time window applies to revenue totals.

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?

One compact sentence with no filler, and the headline fact (organization-wide totals) comes first. It is slightly telegraphic, but nothing needs deleting.

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 read-only aggregation with no output schema, describing the returned dimensions is a reasonable core. However, with three undocumented parameters and no stated filter behavior, an agent cannot determine how to scope a call correctly.

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% for three parameters, so the description must carry the semantics and largely does not. It gestures at per-location and per-coach views, but a reader cannot tell whether passing locationId/coachId filters the totals or whether the breakdowns are unconditional, and organizationId is never mentioned.

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 and payload: organization-wide totals for clients and revenue, broken down per location and per coach. That is enough to distinguish it from a single-coach dashboard or a pure earnings report, but it never names an alternative and the verb is only implied by the tool name.

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 statement of when to use this tool versus get_organization_earnings or get_coach_dashboard_stats, and no exclusions or prerequisites. Usage can only be inferred from the word 'dashboard' and the aggregation summary.

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.