Skip to main content
Glama

list_organization_payments

Read-only

Payments received across the gym (all coaches), newest first. Amounts are in the smallest currency unit.

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

Input Schema

NameRequiredDescriptionDefault
pageSizeNo
pageNumberNo
organizationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 safety is covered. The description adds two genuinely useful behavioral facts beyond annotations: default sort order (newest first) and the currency-unit convention for amounts. It says nothing about pagination behavior despite the tool being paged, and nothing about what a page returns.

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 short sentences, front-loaded with the scope-defining clause and then the currency caveat. Nothing is wasted and nothing is buried.

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?

For a paged, organization-scoped, monetary list tool with no output schema and no parameter descriptions, the definition leaves the agent without pagination guidance or any hint of a result record shape. The currency note is helpful but far from sufficient for correct multi-page invocation.

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% and the description never mentions organizationId, pageSize, or pageNumber. The required organizationId scope and the 1-100 pageSize bound are left entirely to schema inference, so the description fails the burden of compensating for an undocumented schema.

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?

States the resource (payments received) and the scope ('across the gym (all coaches)'), which meaningfully separates it from list_client_payments and list_payments without naming them. No explicit verb, but the title plus 'newest first' make the read-list operation 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 scope phrase 'across the gym (all coaches)' implies when this tool applies versus per-client variants, but no alternative is named and there are no exclusions. The agent must infer the routing rule rather than being told 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.