Skip to main content
Glama

Financial summary (accounting dashboard)

financial_summary
Read-onlyIdempotent

The accounting dashboard's figures for a year: open, paid and overdue invoices, the pipeline (confirmed quotations not yet paid), order confirmations (and confirmed quotations whose order confirmation isn't sent yet), revenue per month (paid, plus the open invoices and the confirmed quotations not invoiced yet) and quotations by status. Net amounts. Admins only, as in docket.

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": "financial_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoDefault: this year

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare it as read-only, idempotent, closed-world, and non-destructive. The description adds meaningful context beyond annotations: admin-only access and precise definitions of metrics like pipeline and revenue-per-month composition. It does not, however, describe response shape or freshness of the figures.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the description is one long run-on sentence with nested parentheticals that make the metric definitions harder to parse. Almost every element is relevant, but the dense structure reduces readability.

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 appropriately carries the burden of explaining what is returned and defines the key aggregates. It covers authorization and the optional year, though it leaves the exact response shape and handling of empty periods implicit.

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 optional 'year' parameter with 100% schema description coverage ('Default: this year'). The description confirms the tool operates on a yearly basis but does not add format, timezone, or boundary semantics beyond the 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?

The description clearly states it returns the accounting dashboard's yearly figures, enumerating invoices, pipeline, order confirmations, monthly revenue, and quotations by status. It distinguishes itself functionally as an aggregate dashboard, though it does not explicitly contrast itself with siblings like revenue_forecast or list_invoices.

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?

It gives an authorization prerequisite ('Admins only') but no guidance on when to choose this tool over alternatives such as revenue_forecast, project_budgets, list_invoices, or list_quotations. The intended use is implied by 'accounting dashboard's figures', but no explicit when/when-not guidance is provided.

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