Skip to main content
Glama

List supported regions

list_supported_regions
Read-onlyIdempotent

Lists all jurisdictions and regions supported by Legis-Link for a specific trade. Use this tool before calling other tools to confirm that the target region is supported, or to discover available regions when the user has not specified one. Returns a structured list of countries and their sub-regions (states, provinces, nations) along with the primary standards that apply in each region.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "trade": "<trade>"
    },
    "name": "list_supported_regions"
  }
}

Input Schema

NameRequiredDescriptionDefault
tradeYesThe trade for which to list supported regions.
api_keyNoLegis-Link API key. Optional: leave empty for the free tier (a daily question limit applies); Pro users paste their ll_p_ key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Legis-Link API key. Optional: leave empty for the free tier (50 requests/day); Pro users paste their ll_p_ key."New value: +"Legis-Link API key. Optional: leave empty for the free tier (a daily question limit applies); Pro users paste their ll_p_ key."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds meaningful context beyond that: it is a preflight validation step and returns countries plus sub-regions plus applicable standards. It does not restate rate-limit behavior, but the schema's api_key field already covers the free-tier limit.

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

Conciseness5/5

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

Three tight sentences: purpose, when-to-use, and return shape, in that priority order. Every sentence contributes and nothing is redundant with the title.

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

Completeness5/5

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

With no output schema present, the description compensates by describing the return value (countries, sub-regions, primary standards). For a single-required-param read tool with full schema coverage, nothing an agent needs to invoke it correctly is missing.

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% and the trade enum is fully enumerated with a description, so the schema carries the parameter semantics. The description only implies the trade parameter ('for a specific trade') without adding format or filtering nuance, so the baseline 3 applies.

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?

States a specific verb and resource ('Lists all jurisdictions and regions supported by Legis-Link for a specific trade') and scopes it to a trade filter. It is clearly distinguishable from all siblings, which are compliance, spec, and document-generation tools rather than discovery lookups.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly prescribes when to call it: 'before calling other tools to confirm that the target region is supported' and 'to discover available regions when the user has not specified one.' Both the preflight and discovery scenarios are named, leaving no inference required.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.