Switch TallyPrime's active reporting period by setting start and end dates, so subsequent report queries use the intended date range until changed again.
Switch TallyPrime's active reporting period. Changes the global from/to date context used by Tally for subsequent report queries until changed again
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | End date in DD-MM-YYYY format | |
| from | Yes | Start date in DD-MM-YYYY format |
Changes observed during successful MCP inspections.
v1.0.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark this tool as read-only (readOnlyHint: true) and not open-world (openWorldHint: false). The description appropriately confirms it changes global context for subsequent queries, which adds value by explaining the scoping effect. However, it does not disclose whether switching periods affects concurrent requests or if there is a default period reset behavior.
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 a single, focused sentence that efficiently conveys the tool's purpose and effect with no wasted words. All key information is front-loaded.
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 the tool is simple (2 params, no output schema), the description covers the essential behavioral details. It explains the global effect and persistence until changed. However, it could mention that date format validation is enforced by the schema, and that the tool is typically used in conjunction with some sibling reporting tools. The score of 4 reflects slight room for improvement in completeness.
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 description coverage is 100%, so the schema already documents both parameters with format hints (DD-MM-YYYY). The description reinforces that these parameters set the global date range for reporting, but does not add new meaning beyond what the schema provides. A score of 3 reflects adequate but not enhanced parameter understanding.
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 the specific verb 'Switch' and clearly identifies the resource as 'TallyPrime's active reporting period'. It further explains that it changes the global from/to date context, which effectively distinguishes this tool from siblings like 'set_company' or 'get_vouchers'.
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?
The description states that the tool is used for subsequent report queries until changed again, implying it should be set before running reports. However, it does not explicitly state when not to use it versus alternatives, nor does it mention any prerequisites like having a company set first.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.