Skip to main content
Glama
Vaquill-AI

canlii-mcp

by Vaquill-AI
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Get Case

get_case
Read-only

Retrieve metadata for a Canadian case including title, citation, decision date, keywords, and URL by providing case and database IDs.

Instructions

Get metadata for a specific case including title, citation, decision date, keywords, and URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
caseIdYesCase ID from list_cases (e.g. "2008scc9")
databaseIdYesDatabase ID (e.g. "csc-scc")
languageNoResponse languageen

Implementation Reference

  • src/server.ts:186-206 (registration)
    Registration of the 'get_case' tool via server.registerTool() with name 'get_case'
    server.registerTool(
	"get_case",
	{
		annotations: { readOnlyHint: true },
		description:
			"Get metadata for a specific case including title, citation, decision date, keywords, and URL.",
		inputSchema: {
			caseId: z.string().describe('Case ID from list_cases (e.g. "2008scc9")'),
			databaseId: z.string().describe('Database ID (e.g. "csc-scc")'),
			language: z.enum(["en", "fr"]).default("en").describe("Response language"),
		},
		title: "Get Case",
	},
	async ({ language, databaseId, caseId }) => {
		try {
			return ok(await request(`/caseBrowse/${language}/${databaseId}/${caseId}/`));
		} catch (e) {
			return err(String(e));
		}
	},
);
  • src/server.ts:199-205 (handler)
    Handler function for the 'get_case' tool - takes language, databaseId, caseId, calls the CanLII API /caseBrowse endpoint
    async ({ language, databaseId, caseId }) => {
	try {
		return ok(await request(`/caseBrowse/${language}/${databaseId}/${caseId}/`));
	} catch (e) {
		return err(String(e));
	}
},
  • src/server.ts:188-197 (schema)
    Input schema for the 'get_case' tool defining caseId, databaseId, and language parameters
    {
	annotations: { readOnlyHint: true },
	description:
		"Get metadata for a specific case including title, citation, decision date, keywords, and URL.",
	inputSchema: {
		caseId: z.string().describe('Case ID from list_cases (e.g. "2008scc9")'),
		databaseId: z.string().describe('Database ID (e.g. "csc-scc")'),
		language: z.enum(["en", "fr"]).default("en").describe("Response language"),
	},
	title: "Get Case",

Tool Definition Quality

A4/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true. The description adds that it returns specific metadata fields, which is consistent and provides additional context beyond the annotation.

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, front-loaded with the action and resource, no wasted words. Efficient and clear.

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

Completeness4/5

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

The tool is simple with no output schema. The description lists return fields, and the schema fully documents parameters. This is sufficient for a straightforward read operation.

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 description coverage is 100%, so the schema already documents all parameters. The description does not add meaning to parameters (e.g., caseId format), but also does not mislead. Baseline 3 is appropriate.

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?

The description clearly states 'Get metadata for a specific case' and lists specific return fields (title, citation, decision date, keywords, URL). It distinguishes from siblings like list_cases and get_case_citations.

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?

The description implies this tool is for retrieving a single case's metadata, but does not explicitly state when to use it versus alternatives (e.g., list_cases for listing or get_case_citations for citations). No when-not or alternative guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Vaquill-AI/canlii-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server