Skip to main content
Glama

Overzicht

get_overview

Retrieves a current bookkeeping overview covering open btw periods and deadlines, unpaid/overdue invoices, missing receipts, profit, tax set-aside, and next actions; also drafts due recurring invoices.

Instructions

The state of the books right now: open btw periods and deadlines, unpaid and overdue invoices, expenses without a receipt, profit this year, an indication of what to set aside for tax, and a list of next actions. Call this first. It also prepares a draft for any recurring invoice that has come due; it never finalizes or sends anything.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false but say nothing about what is written; the description fills that gap precisely — it prepares a draft for any recurring invoice that has come due, and explicitly never finalizes or sends anything. That bounds the side effect and tells the agent a mutating call is safe to make routinely, which the annotations alone could not convey.

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?

Front-loaded with the return contents, then the usage instruction, then the side-effect caveat — a sensible order. The item enumeration is dense but each element carries information; nothing is filler, though the sentence is long.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 carries the burden of describing returns and does so item by item, plus discloses the draft-creation side effect and the entry-point role. For a zero-parameter read-mostly dashboard tool, an agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. The schema is an empty object and the description correctly implies the tool takes no input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (the books' current state) and enumerates exactly what is returned: open btw periods and deadlines, unpaid/overdue invoices, expenses without receipts, profit, tax set-aside, next actions. That enumeration distinguishes it clearly from siblings like list_invoices or year_report, which return single-purpose lists.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Call this first" gives explicit, actionable placement guidance for an agent starting a session. It stops short of naming when *not* to call it or citing a specific alternative for deeper detail, but the intended entry-point role is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.