Skip to main content
Glama

end_day

Finish today's accounts-payable work and advance to the next day, closing the current period so overnight emails, goods receipts, and approval decisions are processed.

Instructions

Finish work for today and move to the next day. New emails, goods receipts and approval decisions arrive overnight. Ending the last day closes the period.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose real behavioral consequences: new emails, goods receipts and approval decisions arrive overnight, and ending the last day closes the period. What it omits is whether the transition is irreversible or what happens to incomplete work left behind, which matters for an unannotated mutation.

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 the action, followed by consequences. No filler, no restatement of the tool name, and each sentence adds a distinct fact.

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, annotation-free state-advancing tool with no output schema, the description covers the essential effect and the overnight arrivals. It would be complete with a note on irreversibility or on what a caller should verify before advancing the day.

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 to convey and the schema is self-explanatory. The baseline applies and the description makes no misleading claims about inputs.

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?

"Finish work for today and move to the next day" names a specific action and its effect, going beyond the name alone by describing what the day transition produces (new emails, goods receipts, approval decisions). It does not explicitly differentiate itself from the sibling close_period, though "Ending the last day closes the period" hints at the relationship without resolving it.

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 description implies the trigger condition (work for today is finished) and notes the period-closing consequence, which gives an agent a usable cue. It never states when not to call it, whether pending approvals or invoices must be resolved first, or that close_period is the alternative for formal period closure.

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