list_jurisdictionsList the jurisdictions and categories LaunchTrust tracks (e.g. EU AI Act, GDPR, US state privacy laws, app-store policies). Public coverage registry. Compliance aid, not legal advice.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already signal safe read-only behavior; description adds context about being a public registry and disclaims legal advice, enhancing transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences, no wasted words, key information front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters and no output schema, description adequately completes the context for a simple listing tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist, so baseline is 4; description does not need to add param info.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool lists jurisdictions and categories with concrete examples, distinguishing it from sibling tools like get_compliance_rules or get_market_report.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies use for exploring tracked jurisdictions but lacks explicit when-to-use or when-not-to-use guidance compared to alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: retrieving rules vs jurisdictions vs scan results vs triggering scans vs verification. No overlap in functionality.
All tool names follow a consistent verb_noun (snake_case) pattern: get_, list_, register_, scan_, verify_. Conventions are uniform throughout.
9 tools cover the essential operations for compliance scanning: registration, scanning (full and quick), results retrieval, history, and verification. The scope feels well-calibrated.
Core CRUD-like coverage is present: register, scan, read results, verify. Missing update/delete for apps or scans is a minor gap but not critical for the domain's primary workflow.