Retrieve IRS tax deadlines and due dates for any tax year. Ensure you never miss filing or payment dates.
Get important IRS tax deadlines and due dates for a given tax year.
| Name | Required | Description | Default |
|---|---|---|---|
| taxYear | No | Tax year (default: 2026) |
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | ||
| error | No | ||
| isError | Yes |
Changes observed during successful MCP inspections.
v1.0.1Input schema / properties / taxYear / descriptionPrevious value: -"Tax year (default: 2025)"New value: +"Tax year (default: 2026)"Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "error": {
+ "additionalProperties": false,
+ "properties": {
+ "code": {
+ "type": "string"
+ },
+ "message": {
+ "type": "string"
+ },
+ "suggestion": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "code",
+ "message",
+ "suggestion"
+ ],
+ "type": "object"
+ },
+ "isError": {
+ "type": "boolean"
+ },
+ "text": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "text",
+ "isError"
+ ],
+ "type": "object"
+}v0.5.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe, non-mutating lookup. The description adds modest scope context ('IRS', 'given tax year', 'important') but does not disclose any additional behavioral traits such as whether the returned list is comprehensive or filtered, or whether state deadlines are excluded.
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, front-loaded sentence with no redundant phrasing. Every word contributes to the agent's understanding of the tool's purpose.
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?
For a simple read-only lookup with one optional parameter, an output schema, and full annotation coverage, the description is largely sufficient. The term 'important' is somewhat vague, and the description does not clarify whether it covers all deadlines or only key ones, but this is a minor gap given the output schema and sibling context.
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?
The schema already documents the only parameter 'taxYear' with its default value, and schema description coverage is 100%. The description rephrases the parameter as 'given tax year' but adds no new semantic detail beyond the schema.
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 clearly states the action ('Get') and the resource ('important IRS tax deadlines and due dates for a given tax year'). It is specific and understandable, but it does not explicitly differentiate from the sibling 'get_personalized_tax_calendar', which may serve a similar need.
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?
No guidance is provided about when to use this tool over alternatives. Siblings like 'get_personalized_tax_calendar' or 'lookup_tax_rule' exist, but the description gives no selection criteria or exclusions, leaving the agent to infer usage from the tool name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.