cs_list_periodsLists accounting periods such as quarters (e.g. 2026-4T) and shows whether each one is open or closed, so you can check before posting entries.
Lista los periodos contables (trimestres, p. ej. 2026-4T) y si están abiertos o cerrados.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
While annotations confirm read-only safety, the description provides crucial behavioral context by stating the status of the periods ('abiertos o cerrados') and gives a specific format example ('2026-4T').
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is highly efficient, front-loading the core function and providing a clarifying example immediately, resulting in zero wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given that it takes no parameters and its safety profile is handled by annotations, the description is fully complete for a simple financial read operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% (zero parameters), so the description is not required to add semantics to input parameters. Baseline 3 is appropriate for a parameter-less tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Lista') and resource ('periodos contables'), clearly distinguishing its function as a financial lookup tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
As a parameter-less tool, it is easy to use. The description provides strong context by defining exactly what is being listed (accounting periods) without needing explicit alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.