Skip to main content
Glama

Get finance summary

get_finance_summary
Read-only

Summarize paid revenue, refunds, platform fees, and booking counts for a date range.

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

Input Schema

NameRequiredDescriptionDefault
to_dateNo
from_dateNo
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that results are aggregated across four metric families for a range, but says nothing about currency, timezone, whether from_date/to_date are inclusive, or what happens when both dates are omitted (all parameters are optional).

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 dense sentence with zero filler, leading with the verb and enumerating the metrics. Nothing is redundant, though it stops short of adding the scoping detail that would make it fully 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 no output schema, the description does the necessary work of naming the four metric families the agent will receive, which is the key return-value information. The remaining gaps are edge-case semantics (default range when no dates are passed, date inclusivity) rather than core omissions.

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 coverage is only 33%: business_id carries a helpful description (id from list_businesses, optional for single-business connections) but from_date and to_date have no schema text at all. The description only says 'for a date range' without defining inclusivity, defaults, or timezone, so it fails to compensate for the coverage gap on the two date parameters.

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 a specific verb (summarize) and names the exact metrics returned: paid revenue, refunds, platform fees, and booking counts, scoped to a date range. An agent can distinguish it from siblings like get_expense or get_business_overview by the aggregate financial metrics, though it never explicitly contrasts with those options.

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: an agent infers it should call this when it needs aggregated financial totals rather than individual records. There is no explicit when-to-use, no when-not-to-use, and no mention of the adjacent tools (get_expense, get_business_overview) that could also surface money figures.

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.

Resources