Skip to main content
Glama

List open accounting periods

crunch_list_accounting_periods
Read-only

List open accounting periods with start/end dates and status to identify where expenses can be created or changed; closed years cannot be edited.

Instructions

List the open accounting periods (financial years) with their start and end dates and status. Expenses can only be created or changed in an open period; closed years can't be edited.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of items
fieldsNoKeep only these fields (dot paths, such as supplier.companyName)
searchNoCase-insensitive substring match on any value

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=false, so the safety profile is covered. The description adds useful domain behavior: closed periods cannot be edited, which explains the significance of the status field. It does not cover pagination, ordering, or whether closed periods are included in the result set.

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?

Two short sentences, front-loaded with what is returned and followed by the domain constraint that motivates use. No filler or repetition of the title.

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 simple read-only list tool with no output schema, the description names the returned fields and the business rule governing them, and the input schema fully documents the three optional filters. Only the open-vs-closed result scope is left slightly ambiguous.

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 100% and all three optional parameters (limit, fields, search) are documented in the schema. The description adds no additional meaning about how these filters interact with the period list, so the baseline of 3 applies.

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 verb and resource (list accounting periods / financial years) plus the returned fields (start date, end date, status). No sibling in the catalog overlaps with this resource, so differentiation is not needed. Minor ambiguity: the title and first clause say 'open' periods, yet 'and status' implies closed ones may also be returned.

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?

The second sentence gives a domain rationale ('Expenses can only be created or changed in an open period; closed years can't be edited'), which implies this is a prerequisite check before creating or modifying expenses. It never explicitly says when to call this tool or what to do with the result, so usage is inferred rather than stated.

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