Skip to main content
Glama
Sign In
itr-agent

itr-agent

by panchasarapavan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

show_ais

Returns the stored AIS as markdown for a specified assessment year, enabling AI apps to display the summary directly to users.

Instructions

Return the stored AIS as markdown. Show the markdown value to the user as it is.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "assessment_year": "<assessment_year>"
    },
    "name": "show_ais"
  }
}

Input Schema

NameRequiredDescriptionDefault
assessment_yearYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the return format (markdown) and a presentation rule (show it verbatim), which is useful, but says nothing about prerequisites, permission/auth needs, or behavior when no AIS exists for the given year. For a no-annotation tool that is a significant gap.

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 short sentences, front-loaded with the action and result, and the second sentence carries a non-obvious display directive rather than filler. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with no annotations and no output schema, the definition omits the ingestion prerequisite, error/empty behavior, and any explanation of the assessment_year argument. The agent is left to guess when the call will succeed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single parameter assessment_year is never mentioned in the description. The schema's pattern and example convey the format, but the description adds no meaning about what the year selects or how it relates to stored AIS records.

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

Purpose4/5

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

States a specific verb and resource: return the stored AIS as markdown. An agent knows what it retrieves and the format. It stops short of distinguishing this read tool from the sibling ingest_ais, and the acronym 'AIS' is never expanded, leaving the resource slightly opaque to an unfamiliar agent.

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

Usage Guidelines3/5

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

Usage is only implied: the tool fetches an already-stored AIS and the agent should display it. There is no explicit when-to-use versus ingest_ais, no statement that ingestion must happen first, and no guidance on what to do if no AIS is stored.

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