Skip to main content
Glama

Lawstronaut

by com.lawstronaut

list_domains

Read-onlyIdempotent

Retrieves a list of domains for a specific jurisdiction and optional filters. Use this tool when: - The user wants to find legal domains for a specific jurisdiction and optional filters - The user asks about available domains for a domain name - The user wants to filter with pagination

Parameters:
- domain (optional): Filter domains by name
- limit: z.number().optional().describe("Number of results to return"),
- offset: z.number().optional().describe("Number of results to skip")

Returns:
- List of domains with domain_id, domain, pagination: total_count, limit, offset
- Only returns domains that have data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results to return
domainNoFilter by domain name
offsetNoNumber of results to skip

TDQS

A3.9/5.0
Behavior4/5

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

Description 'Retrieves' aligns with annotations' readOnlyHint=true, and adds behavioral detail like 'Only returns domains that have data' and pagination behavior, which are not in annotations.

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

Conciseness3/5

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

The description is structured but somewhat verbose, including a 'Parameters' section that largely duplicates the schema, and a 'Returns' section; could be more concise.

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

Completeness3/5

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

Description provides a 'Returns' section compensating for no output schema, but introduces ambiguity with 'jurisdiction' which is not a parameter in the schema. Otherwise covers main usage and behavior.

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 baseline is 3. Description repeats schema parameter descriptions but adds context about optionality and grouping, without adding new semantic meaning beyond schema.

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' and resource 'list of domains', and specifies 'for a specific jurisdiction and optional filters', which distinguishes it from sibling tools like list_documents or list_jurisdictions.

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 explicitly lists three use cases for when to use this tool, but does not mention when not to use it or alternative tools, though the context is clear.

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