Skip to main content
Glama

Get ITIN Status

get_itin_status
Read-only

Returns where the ITIN (Individual Taxpayer Identification Number) application for the company's members stands with doola: itinStatus is Not started, Payment processing, In review, Submitted to the IRS or Completed. When offerAllowed is true it also returns a quizLink to doola's ITIN service; mention that service only then, and only with that exact link. Never tell the user whether they qualify for an ITIN: the quiz decides that. Answer in plain language and never show the user the field names.

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

Input Schema

NameRequiredDescriptionDefault
contextNoOptional, for analytics only. In one sentence, why you are calling this tool and how it serves the user's goal. Describe the purpose in general terms: never include names, emails, phone numbers, addresses, IDs or any other personal details.
llm_modelNoOptional, for analytics only. Your exact model identifier from your system prompt (e.g. "claude-opus-4-8"), or "unknown" if unsure. Never guess.
conversation_idNoOptional, for analytics only. The exact conversation_id from this server's previous response, unchanged. The first response provides one, so leave this out until you have it and never invent one. Keep passing the same value for the rest of the conversation, even when the user moves on to a new request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the read-only, closed-world, non-destructive profile, and the description adds real substance on top: the returned status vocabulary, the conditional quizLink, and two hard constraints (don't judge eligibility, don't expose field names). That is behavior beyond what the annotations convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the status enumeration, then the conditional link rule, then the guardrails. Dense but every sentence carries a rule; the enum list of five statuses is the only mildly verbose element.

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

Completeness5/5

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

There is no output schema, so the description appropriately explains the return shape (itinStatus values plus quizLink and offerAllowed) and the presentation constraints. Nothing an agent needs in order to call and use this tool correctly is missing.

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

Parameters3/5

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

Schema coverage is 100% and each of the three optional analytics parameters is fully documented in the schema, so the baseline applies. The description adds nothing about them, though they are analytics-only and need no elaboration.

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?

States a specific verb and resource ('Returns where the ITIN ... application for the company's members stands with doola') and enumerates the exact status values, so an agent can distinguish it from sibling status tools like get_ein_application_status or get_tax_filing_status without opening the schema.

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?

Gives explicit conditional guidance: mention the ITIN service only when offerAllowed is true and only with the exact quizLink, and never state whether the user qualifies. It does not name sibling tools or say when to prefer them, so it stops short of full alternative routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.