Skip to main content
Glama

ITIN Finance

by io.github.bguillow-rgb

find_itin_lenders

Read-only

List institutions that accept ITIN (no SSN) applicants for a loan or card type, optionally filtered by US state. Every entry states whether it was verified against the institution's own pages, with citation URLs and dates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoAnswer language: en (default) or es (Spanish)
stateNoUS state name or 2-letter code
loan_typeYesWhich product the question is about: auto loan, mortgage, personal loan, business loan, or credit card

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the description doesn't need to repeat that. It adds value by noting entries include verification status with citation URLs and dates, which is a behavioral/output trait beyond annotations.

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, no fluff, front-loaded with the main purpose. The second sentence adds essential detail about output verification. Efficient and well-structured.

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?

The tool is simple with 3 parameters, all described. The description covers the core functionality and output characteristics. Without an output schema, it could mention response format, but the verification detail mitigates that. Adequate for the complexity.

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%, so the schema documents all parameters. The description reiterates 'loan or card type' and 'optional state filter' but adds no new meaning beyond the schema, hence baseline 3.

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 clearly states the tool lists institutions accepting ITIN for a loan or card type, with an optional state filter. It distinguishes from siblings like get_lender_details (which focuses on specifics) by emphasizing the list and verification aspect.

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?

The description implies when to use it (for listing institutions) but does not explicitly name alternatives like get_lender_details for details. It provides clear context without exclusions, so a 4 is appropriate.

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

All ITIN Finance toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation3/5

Most tools target distinct content types, but there is meaningful overlap between can_i_get_this_loan and find_itin_lenders, and between faq_lookup and search_guides. The descriptions help clarify boundaries, but an agent could still hesitate when choosing the right search/retrieval tool.

Naming Consistency2/5

Tool names do not follow a consistent verb_noun pattern: can_i_get_this_loan and how_to_get_an_itin are question-style phrases, while others use get_, find_, search_, or noun-only names like itin_state_info. All names are readable, but the conventions are too mixed to predict new tool names.

Tool Count5/5

Eight tools is well-scoped for an ITIN finance information service. Each tool covers a distinct aspect of the domain—eligibility, lenders, guides, FAQs, state context, and ITIN application—without feeling bloated or thin.

Completeness5/5

The tool surface covers the core user journeys: finding guides, searching FAQs, checking loan eligibility, discovering lenders, getting lender details, learning how to get an ITIN, and understanding state-level context. No major dead ends or obvious missing operations are apparent for this informational domain.

Resources