Skip to main content
Glama
Sign In
itr-agent

itr-agent

by panchasarapavan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

generate_itr_json

Generates ITR JSON in the exact e-Filing portal format from validated income-tax data, so AI apps can prepare filings after validation.

Instructions

Generate the ITR JSON in the exact shape the e-Filing portal expects. Input must already pass validate_itr.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the behavioral burden. It discloses the prerequisite and target format, but does not explain whether the JSON is returned inline or written elsewhere, how errors are handled, or other side effects; the output schema covers the return shape.

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?

Two sentences are used with no wasted wording. The purpose is front-loaded, followed by the essential prerequisite, making the definition easy to scan.

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 parameterless generator with an output schema, the description covers the key prerequisite and output expectation. It could be slightly more complete by mentioning error behavior or whether the generated JSON is returned directly, but nothing critical for invocation is missing.

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 has zero input parameters and the schema is empty, so there are no parameter semantics to clarify. The description appropriately does not invent parameter details, matching the baseline for parameterless tools.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: "Generate the ITR JSON." It also specifies the output shape ("exact shape the e-Filing portal expects") and distinguishes the tool from its validate_itr sibling by requiring validation first.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage context by requiring that input "must already pass validate_itr," effectively routing the agent to validate first. It does not explicitly describe when not to use the tool or what happens if validation has not passed, so it falls short of the top score.

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

Deploy Server

Other Tools