Skip to main content
Glama

Lawstronaut

by com.lawstronaut

list_portals

Read-onlyIdempotent

Retrieves a list of legal portals filtered by jurisdiction and optional criteria. Use this tool when: - The user wants to find legal portals, websites, or resources for a specific jurisdiction - The user asks about available portals in a country or state - The user wants to filter portals by name, language, or tag with total crawled links

Parameters:
- iso (required): Filter by Jurisdiction ISO code (e.g. "US").
- name (optional): Filter portals by name or URL keyword
- tag (optional): Filter portals by tag
- lang (optional): Filter portals by language name

Returns:
- List of portals with name, URL, language, jurisdiction, tags, and total crawled links
- Only returns portals that have crawled data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
isoYesFilter by Jurisdiction ISO code (e.g. 'US')
tagNoFilter by portal tags
langNoFilter by language
nameNoFilter by portal name

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate readOnly, idempotent, non-destructive. The description adds value by stating 'Only returns portals that have crawled data,' which is a behavioral filter not captured by annotations.

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?

Well-structured with a main sentence, bulleted use cases, and parameter list. No redundant or unnecessary content.

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?

Given no output schema, the description lists return fields and notes the condition of crawled data. Lacks mention of pagination or limits, but adequate for a list tool with moderate complexity.

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

Parameters4/5

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

Schema coverage is 100% but the description adds meaning: for 'name' it says 'keyword' implying partial match, and groups parameters with filtering intent. This goes beyond schema descriptions with a baseline of 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 verb 'Retrieves a list' and the resource 'legal portals' with jurisdiction filtering. It distinguishes from sibling list_ tools (e.g., list_jurisdictions, list_documents) by focusing on portals and specific criteria.

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?

Three explicit 'Use this tool when:' bullets provide clear use cases. Does not state when not to use or name alternative tools, but the context is clear enough for an agent given sibling tools.

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

All Lawstronaut 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.7/5.0
Disambiguation4/5

Most tools have distinct purposes, but evidence_pull and get_document_text both return full text, which could cause confusion. Other tools like list_documents and get_markdown are clearly differentiated.

Naming Consistency3/5

Names follow a mix of 'list_', 'get_', and one-off names like 'evidence_pull' and 'horizon_scan'. The verb_noun pattern is present but inconsistent.

Tool Count4/5

16 tools is reasonable for a legal document retrieval server, though some functionality overlaps (e.g., multiple ways to get document text). Still well-scoped for the domain.

Completeness4/5

Covers browse, filter, and retrieve operations comprehensively. Missing a general text search tool, but horizon_scan offers a recent-changes scan. Minor gap.

Resources