Skip to main content
Glama

get_organization_earnings

Read-only

Gym earnings statement for a period: total, per-coach totals, and each payment with who sold it and who coaches that client now, plus the payout mode. Amounts are in the smallest currency unit. Payouts are settled outside the app.

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

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
organizationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds genuinely useful behavior beyond that — amounts are in the smallest currency unit, and payouts are settled outside the app, which warns the agent not to treat these figures as in-app payouts. It does not cover pagination or whether partial-period data is returned, keeping it short of a 5.

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?

Three tight sentences: the return content leads, then the currency-unit convention, then the settlement caveat. Every clause carries information an agent would otherwise have to guess, and nothing is repeated from the annotations.

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 no output schema, the description takes on the job of explaining returns and does it well by listing total, per-coach totals, per-payment attribution, and payout mode. The remaining gap is input-side: the date range and required organizationId are left for the agent to infer from the bare schema.

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%, so the description must carry the burden for all three parameters, and it largely fails: "for a period" only loosely implies from/to, with no date format, timezone, inclusivity of bounds, or default range given. organizationId is never mentioned at all despite being required.

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 ("gym earnings statement for a period") and enumerates what it contains: total, per-coach totals, per-payment seller/current coach attribution, and payout mode. That is far more specific than a tautology and lets an agent distinguish this aggregate earnings report from the sibling list_organization_payments, though it never names that sibling explicitly.

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?

Usage is only implied: the tool is scoped "for a period," which suggests calling it when a date-bounded earnings summary is needed, and the per-payment breakdown hints at how it differs from a plain payments list. There is no explicit when-to-use/when-not guidance and no named alternative, so an agent must infer the routing from the return-shape description.

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.