Skip to main content
Glama

profit_and_loss

Read-only

Resultatopgørelse (profit and loss) for a period: revenue and expense lines, result (øre).

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": {
      "connection_id": "<connection_id>",
      "date_from": "<date_from>",
      "date_to": "<date_to>"
    },
    "name": "profit_and_loss"
  }
}

Input Schema

NameRequiredDescriptionDefault
date_toYes
date_fromYes
connection_idYesId from list_connections

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, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine value beyond that by saying what the response contains (revenue and expense lines plus a result) and the unit (øre), which matters since there is no output schema. It does not disclose accrual basis, whether zero lines are included, or rounding behavior.

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?

A single front-loaded sentence that identifies the report, its time scope, and its contents with no filler. It is lean to the point of omitting guidance an agent would want, but nothing written is wasted.

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 three-required-parameter read-only report with no output schema, the description covers the essentials: what it produces and in which unit. Gaps remain around range semantics, currency/accounting basis, and how it differs from vat_by_quarter, which matter for correct invocation.

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?

Schema description coverage is only 33% (only connection_id is documented, pointing to list_connections). The phrase "for a period" implies date_from/date_to form an inclusive range, which is a small but real addition; however, it clarifies neither boundary inclusivity nor timezone/format expectations beyond the schema's date format.

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?

Names a specific resource (Resultatopgørelse / profit and loss) and states its scope ("for a period") plus the contents returned (revenue and expense lines, result in øre). An agent can tell this is a financial statement report rather than an invoice or VAT listing tool. It stops short of explicitly contrasting with vat_by_quarter, so it is clear but not fully sibling-differentiated.

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 when-to-use guidance and no mention of alternatives such as vat_by_quarter, which is the closest sibling and could plausibly be confused with this report. The only usage signal is the implied date range in "for a period".

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