lawyer-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LEGALIZE_API_KEY | Yes | API key for Legalize.dev. Can be raw token (leg_...) or 'Bearer leg_...'. | |
| LEGALIZE_TOOLSET | No | Set to 'minimal' to reduce toolset size. | |
| LEGALIZE_BASE_URL | No | Base URL for Legalize.dev API (default: https://legalize.dev). | |
| LEGALIZE_HTTP_RETRIES | No | Number of HTTP retries (default: 2). | |
| LEGALIZE_HTTP_TIMEOUT | No | HTTP timeout in seconds (default: 30). | |
| LEGALIZE_SSL_INSECURE | No | Set to '1' to disable certificate verification (not recommended). | |
| LEGALIZE_SSL_CERT_FILE | No | Path to CA bundle for TLS certificate verification. | |
| LEGALIZE_ENABLE_DANGEROUS_TOOLS | No | Set to '1' to enable dangerous tools like rotate key. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| legalize_openapi_summaryA | Public: summarize the Legalize.dev OpenAPI spec (endpoints, versions). No API key required. |
| legalize_countriesB | List supported countries. |
| legalize_jurisdictionsB | List jurisdictions within a country. |
| legalize_lawsA | Search/list laws within a country (single page). |
| legalize_laws_allB | Search/list laws within a country, automatically paging until exhaustion or max_pages. Returns raw page payloads plus a best-effort flattened list when the API returns an array or a {items|data|results} container. |
| legalize_law_metaC | Get metadata for a law (lightweight endpoint). |
| legalize_law_getC | Fetch a full law payload. |
| legalize_reformsB | List reforms (diffs) for a law, newest-first; useful for change tracking. |
| legalize_commitsB | List git commits for a law repository (lightweight history). |
| legalize_law_at_commitA | Fetch the law content as it was at a specific git commit SHA. |
| legalize_rangosB | List the legal hierarchy/ranks (rangos) for a country. |
| legalize_statsA | Get summary statistics for a country (optionally filtered by jurisdiction). |
| legalize_accountA | Get account usage/limits info for the current API key (does not count against quota). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool targets a distinct resource or action: metadata vs full law, paginated vs single-page search, diffs vs git history. The pagination variant (laws_all) is clearly differentiated from laws, and the hierarchy/rank tool is unique. No two tools appear to do the same thing.
All 13 tools share the consistent `legalize_` prefix and use snake_case. The suffix pattern is predictable: simple resource names (countries, laws) or resource_qualifier (law_get, law_at_commit). Even the paginated variant follows a clear `_all` suffix, making the naming scheme uniform and easy to navigate.
13 tools is well within the ideal 3-15 range for a domain-specific API client. Each tool addresses a distinct need, from listing countries to retrieving historical law content, with no redundancy or bloat.
The tool set provides comprehensive read-only coverage of the Legalize.dev API: discovery (countries, jurisdictions, rangos), search (laws, laws_all), retrieval (law_get, law_meta), change tracking (reforms, commits, law_at_commit), and account management (account). No obvious gaps exist for the stated purpose of legal information retrieval.