Skip to main content
Glama
Sign In
canlii-mcp

canlii-mcp

by tomilashy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Case Databases

list_case_databases
Read-only

Discover all courts and tribunals in the CanLII collection, complete with their database IDs for use in legal research.

Instructions

List all courts and tribunals in the CanLII collection with their database IDs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_case_databases"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoResponse languageen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description's 'List' wording is consistent. It adds scope context (all courts/tribunals, database IDs) but does not provide additional behavioral details like pagination or response format.

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?

Single sentence, starts with the verb, contains zero filler, and fully conveys the operation in a clear front-loaded manner.

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?

Low complexity (one optional param), schema covers all params, readOnly annotation present, and description states the resource scope and output fields; no major gaps.

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 fully documents the single optional language parameter (100% coverage, enum en/fr, default en). The description adds no parameter-specific information, so 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?

Description uses specific verb 'List' with resource 'courts and tribunals in the CanLII collection' and output 'database IDs', clearly distinguishing from sibling list_legislation_databases which covers a different resource.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus list_legislation_databases or list_cases; usage is only implied by the clear resource scope. No alternatives or exclusions are mentioned.

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

Deploy Server

Other Tools