Skip to main content
Glama

run_ca_company_filings

Fetch certificates and filings for a federal corporation from the Corporations Canada registry, returning date, type, and amendment details by corporation number or URL.

Instructions

Certificates and filings of one federal corporation in the Corporations Canada registry: date, type and amendment details. 1 point per returned record.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>"
    },
    "name": "run_ca_company_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesCorporation number or registry URL. e.g. 426160-7
max_itemsNoMax items (up to 250)
start_pageNoStarting page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the credit cost ('1 point per returned record') and the return fields, but says nothing about read-only nature, pagination beyond the schema hints, or auth requirements. Partial but not rich behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with no filler, and the resource scope is front-loaded before the return fields and cost. Efficient, though the credit-cost sentence could be more integrated.

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?

For a 3-param read tool with no annotations or output schema, the description compensates reasonably by enumerating the returned fields (date, type, amendment details) and the per-record cost. Only minor gaps around pagination behavior and permissions remain.

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 company, max_items, and start_page. The description adds no format or syntax detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (certificates and filings of one federal corporation in the Corporations Canada registry) and the fields returned (date, type, amendment details). It clearly distinguishes itself from run_ca_companies / run_ca_companies_search by being about filings of a single corporation, though it doesn't name the siblings explicitly.

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?

Usage is implied by 'one federal corporation' and the singular 'company' input, but there is no explicit when-to-use guidance or comparison to the sibling companies/search tools. An agent can infer the intent but gets no routing help.

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