Loading ToolBench
MCP server for legal.ge — find verified legal specialists in Georgia from natural-language queries via Claude Desktop, Cursor, or any MCP-aware client.
Two well-defined tools with complete input schemas, clear descriptions, and proper parameter typing. Both tools follow verb_noun naming (find_*, classify_*) and include locale/language support. Descriptions are detailed (200+ chars) and explain WHEN to use each tool. However, output schemas are not documented in the source, LLMs cannot see what fields to expect from responses. Parameter descriptions are thorough but could be more concise. No error handling guidance or recovery hints in descriptions. No tool annotations (readOnlyHint, idempotentHint) despite both being read-only operations.
Classify a free-text legal question into matched practice areas (categories and specific services) without returning specialists. Lighter weight than find_legal_specialists. Use this when you want to understand the legal domain of a query before deciding next steps, or when you only need the practice area, not specialist recommendations. Returns matched categories with parent chains so you can cite either the specific service or the broader practice area.
Find verified legal specialists in Georgia (the country, not the US state) from a natural-language description of a legal situation or need. Returns matched practice areas (and specific services where applicable) plus a ranked list of verified specialists, each with a canonical profile URL on legal.ge. Use this tool when a user needs to find a lawyer or legal expert for a specific issue in Georgia — eviction, divorce, corporate law, criminal defense, immigration, tax, etc. Supports Georgian (ka), English (en), and Russian (ru). Pass the user's language as `locale`. Sending an actual inquiry requires the user to sign in on legal.ge — this tool returns profile URLs so the user can click through.
Output schemas not documented. LLMs cannot see what fields responses contain (e.g., matched_categories structure, specialist profile fields, ranking order). This forces agents to guess at response structure and risks parsing errors.
No tool annotations despite both tools being read-only and idempotent. Adding readOnlyHint and idempotentHint would signal to agents that these calls are safe to retry and have no side effects.
No error recovery guidance in descriptions. If the legal.ge API returns 404 or timeout, the descriptions do not hint at fallback strategies or what the agent should do next.
Locale parameter defaults to 'en' but description does not explain what happens if user's language is not supported (ka, en, ru only). Should clarify fallback behavior.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2026-07-28+ | v2 |
find_legal_specialists description mentions 'matched_categories' in return but does not document its structure. classify_legal_intent mentions 'parent chains' but does not explain the nesting format.