Timix.AI

Reopen billing month

reopen_month

DestructiveIdempotent

Reopen a previously closed billing month, allowing time to be logged and edited again. Call once with no token to preview; re-call with the returned confirm_token and an idempotency_key to commit. Reversible only by closing the month again.

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

Input Schema

Name	Required	Description
`year`	Yes	Calendar year of the month to reopen (e.g. 2026).
`month`	Yes	Calendar month to reopen (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.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds the genuinely non-obvious behavior: the preview/commit handshake and the fact that the change is undone only by re-closing. It stops short of saying what the preview returns or what state the month lands in.

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 tight sentences: effect first, procedure second, reversibility last. Nothing is repeated and the preview-first instruction is front-loaded where an agent will read it before calling.

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, no-output-schema mutation with 100% schema coverage, the description covers the critical decision points: preview before commit, idempotency for retries, and how to undo. Minor gap: it does not describe what the preview response contains beyond the token.

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 already explains confirm_token, its ~10 minute expiry, and idempotency_key retry semantics. The description reinforces the token flow but introduces no parameter detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb (reopen) and resource (closed billing month) plus the concrete consequence: time can be logged and edited again. That effect clause is what separates it from close_month and reopen_timesheet at a glance.

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 an explicit two-step procedure: call once with no token to preview, then re-call with confirm_token and idempotency_key to commit. It also names the exit path ('reversible only by closing the month again'), which implies close_month as the undo, though it does not name that sibling outright.

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?