Cipo

Get Cipo Patent

get_cipo_patent

Read-onlyIdempotent

Look up one Canadian patent or application by number in the Canadian Patents Database (CIPO) and get its full bibliographic record: title (English/French), current status, filing date, issue/grant date (blank if not yet granted), owners, applicants, inventors and IPC classification. Accepts the number with or without a "CA" prefix, spaces or dashes — digits only, up to 7 digits.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

Name	Required	Description	Default
`number`	Yes	Canadian patent/application number, e.g. "2553707" or "CA 3265179".

Output Schema

Name	Required	Description	Default
`title`	No
`owners`	No
`source`	No
`status`	No
`inventors`	No
`applicants`	No
`filing_date`	No
`patent_number`	No
`ipc_classification`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The annotations already disclose read-only, idempotent, non-destructive, and open-world behavior, lowering the burden on the description. The description adds useful behavioral context such as the fields returned and that the issue/grant date is blank if not yet granted, though it does not mention not-found behavior or rate limits.

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?

The description is two tightly written sentences that front-load the purpose and then clarify input format. Every sentence carries useful information with no filler.

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?

For a single-record lookup tool with rich annotations and an output schema, the description provides sufficient context: what it retrieves, the fields returned, and the accepted input formats. Error behavior is not described, but the output schema and annotations cover enough that the definition is complete for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single parameter is already exemplified in the schema. The description adds meaningful format guidance beyond the schema by saying the number may include a "CA" prefix, spaces, or dashes, and that the digits are up to 7 digits long.

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 states a specific verb and resource: look up one Canadian patent or application by number in CIPO. It also specifies the return payload (full bibliographic record) and distinguishes this single-record lookup from a general search by emphasizing "one ... by number."

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

Usage Guidelines4/5

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

The description gives clear usage context by stating that the tool is used when a patent/application number is available. However, it does not explicitly name search_cipo_patents as the alternative for non-number queries or state when not to use this tool, so it falls short of a 5.

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

All Cipo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.