canido
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CANIDO_API_KEY | Yes | Your CanIDo API key for accessing the regulatory intelligence API. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_requirementsA | Look up what permits, licenses, and regulatory requirements are needed for a business activity in a specific location. Returns detailed requirements including fees, agencies, processing times, prerequisites, and common gotchas. |
| list_locationsA | List all locations (cities) currently supported by CanIDo for regulatory lookups. |
| get_requirement_detailA | Get detailed information about a specific permit or requirement by its ID. |
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 3 tools
Each tool has a clearly distinct purpose: looking up requirements for a business activity, listing supported locations, and getting details on a specific requirement. No overlap exists.
All tool names follow a consistent verb_noun pattern (get_requirement_detail, list_locations, lookup_requirements), making it easy to understand what each tool does.
With only 3 tools, the server is on the lower end but still reasonable for a focused domain of regulatory lookups. However, it may feel thin if more operations are needed.
The tools cover core needs (lookup, location listing, detail) but lack obvious operations like searching requirements, comparing locations, or managing user data. Gaps exist but are workable.