Find Indian-American immigration attorneys & law firms.
Provide a point (`lat`+`lng`, optional `radius_miles`) or `city`/`state`. Filter by `tag`
(e.g. "immigration").
| Name | Required | Description | Default |
|---|---|---|---|
| lat | No | ||
| lng | No | ||
| tag | No | ||
| city | No | ||
| limit | No | ||
| state | No | ||
| offset | No | ||
| open_now | No | ||
| radius_miles | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / properties / offsetAdded value: +{
+ "default": 0,
+ "title": "Offset",
+ "type": "integer"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full responsibility for behavioral disclosure. It does not mention authentication, rate limits, side effects, pagination, or the format of results (just 'Find'). The schema includes parameters like 'open_now', 'limit', and 'offset' that are not mentioned, leaving the agent unaware of these capabilities or constraints.
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 exceptionally concise: two sentences that immediately state purpose and key usage. Every sentence is necessary and front-loaded with the most critical information. No wasted words.
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?
Considering the tool has 9 parameters, no required ones, an output schema, and many siblings, the description is insufficiently complete. It does not explain pagination ('limit', 'offset'), the 'open_now' filter, or what the output contains. For a listing tool, this forces the agent to guess or rely on conventions from sibling tools.
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?
Schema description coverage is 0%, so the description must add meaning. It explains that 'lat' and 'lng' define a geographic point, 'radius_miles' is optional, and 'city'/'state' are alternatives, with 'tag' for filtering. These explanations add value beyond schema names. However, it ignores 'limit', 'offset', and 'open_now', leaving 4 of 9 parameters unexplained.
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 states the tool's purpose: 'Find Indian-American immigration attorneys & law firms.' It specifies the types of resources (attorneys, law firms) and the domain (Indian-American immigration), making it easy for an agent to understand what the tool retrieves. The name and description together distinguish it from siblings like 'get_legal_details' (likely a detail retrieval) and 'search_legal_by_text' (text search).
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 provides explicit guidance on how to use the tool: 'Provide a point (lat+lng, optional radius_miles) or city/state. Filter by tag (e.g. 'immigration').' This tells the agent the two primary modes of querying (location or city/state) and optional filtering. However, it does not specify when to use this tool versus alternatives like 'search_legal_by_text', nor does it mention prerequisites or limitations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.