Skip to main content
Glama

close_period

Closes the current accounting period and finalizes period-end processing; only permitted on the last day.

Instructions

Close the period. Only allowed on the last day.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It never states that closing a period is a state-mutating, effectively irreversible operation, what gets locked as a result, or whether permissions are required — the one constraint given ('last day') is the only behavioral disclosure.

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 the action and immediately followed by the constraint; no wasted words. It is under-specified rather than verbose, which is a completeness problem rather than a structure one.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-annotation, mutation-style operation with no output schema, the description should explain consequences, irreversibility, and required preconditions. It supplies only the day restriction, leaving the agent unable to predict the effect of calling it or what happens to the closed period afterward.

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 semantics to explain and the baseline of 4 applies. The only minor gap is that the description does not clarify that no period identifier is needed because the current period is implied.

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 and resource ("Close the period"), which an agent can distinguish from read-oriented siblings like get_status or list_invoices. It stops short of saying which period (implicitly the current one, since it takes no parameters) or what 'close' means in this system, so it is clear but not disambiguated against the wider catalog.

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?

"Only allowed on the last day" gives a real precondition for invocation, which is more than most definitions offer. However, there is no mention of prerequisites (approvals, open invoices), no alternative tools for related period operations, and no statement of what to do if it is not the last day.

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