Look up common IRS tax forms by number to learn their purpose, who needs them, and where to find them.
Get information about common IRS tax forms — what they are, who needs them, and where to find them.
| Name | Required | Description | Default |
|---|---|---|---|
| formNumber | Yes | IRS form number (e.g., '1040', 'W-2', '1099-NEC', 'Schedule C') |
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | ||
| error | No | ||
| isError | Yes |
Changes observed during successful MCP inspections.
v1.0.1Output 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 establish that this is a safe, read-only, idempotent operation. The description adds useful context about the scope ('common' forms) and the nature of the returned content (explanations, audience, and sources), which goes beyond the bare annotations without contradicting them.
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 sentence with no filler. The main action and resource are front-loaded, and the em-dash efficiently enumerates the three kinds of information provided.
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 low-complexity tool with one parameter and an output schema, the description covers the essential purpose and content areas. It is slightly incomplete in that it does not clarify which forms are considered 'common' or how this relates to filing-format guidance from siblings, but this is a minor gap.
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 input schema already documents the single parameter formNumber with helpful examples, so the description carries little parameter burden. It does not add any additional semantic detail about the parameter, justifying the baseline score for high schema coverage.
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 identifies the verb ('Get information') and resource ('IRS tax forms'), and adds the scope qualifier 'common' to narrow the topic. It does not explicitly distinguish itself from the closely related sibling get_form_filing_guide, so it stops short of a 5.
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 implies the tool is for general lookup of IRS form information—what forms are, who needs them, and where to find them—but it gives no explicit guidance on when to prefer this tool over siblings like get_form_filing_guide or lookup_tax_rule. No alternatives or exclusions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.