Skip to main content
Glama

Business overview

crunch_get_overview
Read-only

Fetch a one-call business snapshot: company/VAT details, bank and card balances, invoice totals, and open accounting periods to answer how the business is doing.

Instructions

A one-call snapshot of the business: company and VAT details, bank account and credit card balances, sales invoice totals (invoiced and outstanding) and open accounting periods. A good first call for questions like "how is my business doing?".

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds that this is a single aggregate call rather than a paginated list, and enumerates the exact data sets returned. It does not mention authentication requirements or whether figures are live vs cached, which would be the remaining useful behavioral detail.

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 sentences, front-loaded with the core identity ('a one-call snapshot of the business') and then the contents, ending with the concrete use case. Every clause carries information and there is no filler.

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 and no parameters, the description carries the burden of describing return content, and it does so by enumerating the five data groups an agent will receive. It does not indicate response shape or ordering, but for a zero-parameter read-only aggregate this is largely sufficient.

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?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The schema itself forbids additional properties, and the description correctly implies no filtering or scoping options exist.

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 resource and form: 'a one-call snapshot of the business', then enumerates exactly what is included (company/VAT details, bank and card balances, invoiced and outstanding invoice totals, open periods). The 'one-call snapshot' framing implicitly sets it apart from the granular sibling getters (crunch_get_company_details, crunch_get_vat_summary, crunch_get_invoice_totals), though no sibling is named.

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?

Gives a concrete trigger: 'A good first call for questions like "how is my business doing?"', which is enough for an agent to route broad business-status questions here rather than to individual getters. It offers no explicit when-not guidance or named alternative for narrower questions, so it stops short of a 5.

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

Deploy Server

Other Tools