Skip to main content
Glama

Get default invoice note

crunch_get_default_invoice_note
Read-only

Retrieve the default note Crunch prints on new sales invoices, so you can review or confirm standard payment instructions before creating invoices.

Instructions

Get the default note Crunch prints on new sales invoices (often payment instructions).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.7/5.0
Behavior3/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 and the description is not required to restate it. The parenthetical '(often payment instructions)' usefully characterizes the content being returned, but nothing is said about what happens when no default note is configured or what type the value is.

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?

A single front-loaded sentence with the resource scope stated first and a short clarifying parenthetical; no filler or redundancy.

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?

For a zero-parameter, single-value read with no output schema, the description conveys enough to invoke it correctly. A brief note on the return type or the empty/unset case would close the remaining gap.

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, so there is no parameter meaning for the description to add; the schema is trivially complete. This earns the baseline score for a no-parameter tool.

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 states a specific verb ('Get') and a precisely scoped resource ('the default note Crunch prints on new sales invoices'), which disambiguates it from the invoice-retrieval siblings by emphasizing 'default' and 'new' invoices. It is clear what is fetched, though it never explicitly contrasts itself with a sibling such as crunch_get_invoice.

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 can infer it should call this when it needs the standard note template applied to future invoices. There is no explicit when-to-use/when-not statement, no mention of prerequisites (e.g. authentication via crunch_auth_start), and no named alternative.

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