Timix.AI

Close billing month

close_month

DestructiveIdempotent

Close a billing month so no further time can be logged or edited in it. Call once with no token to preview; re-call with the returned confirm_token and an idempotency_key to commit. Reversible only by reopening the month.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": "<year>",
      "month": "<month>"
    },
    "name": "close_month"
  }
}

Input Schema

Name	Required	Description
`year`	Yes	Calendar year of the month to close (e.g. 2026).
`month`	Yes	Calendar month to close (1-12).
`confirm_token`	No	Token returned by the preview (call this tool once with no token to get it). Required to commit; expires in ~10 minutes.
`idempotency_key`	No	Required when committing (confirm_token present): retrying with the same key returns the original result instead of acting twice.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 15, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, and the description adds context those flags cannot convey: the exact effect of closing (no logging or editing), the reversibility path (only reopening), and the mandatory preview-before-commit safety pattern. That is substantive behavioral disclosure for a destructive operation.

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?

Three short sentences, front-loaded with purpose and effect, then the commit workflow, then reversibility. No filler and nothing repeated.

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 destructive, gated mutation with no output schema, the description covers the full call sequence and the reversibility constraint, which is what an agent needs to invoke it correctly. It stops short of describing what the preview response contains besides the token, so an agent cannot fully anticipate the preview output.

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 coverage is 100% and the property descriptions already explain confirm_token's origin and expiry and idempotency_key's retry semantics. The description's mention of the token/no-token distinction and the idempotency_key largely restates what the schema documents, so it adds little beyond baseline.

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 gives a specific verb and resource ("Close a billing month") and immediately states the operational consequence: no further time can be logged or edited. It also names its inverse path ("Reversible only by reopening the month"), which lets an agent distinguish this from reopen_month without opening either schema.

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?

The description prescribes an explicit two-step sequence: call with no token to preview, then re-call with the returned confirm_token plus an idempotency_key to commit. That is clear when-and-how guidance for the primary flow, though it doesn't state preconditions such as whether pending timesheets must be approved first.

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

All Timix.AI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?