API Ninjas

searchCanadaRoutingNumbers

Read-only

Finds Canadian bank branches and their routing numbers by bank name, city, province or postal code. To decode a known routing number use /canadaroutingnumber. Requires a premium subscription.

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": "searchCanadaRoutingNumbers"
  }
}

Input Schema

Name	Required	Description
`city`	No	City name to search for branches. Premium only.
`offset`	No	Number of results to offset for pagination. Available for annual subscriptions only.
`province`	No	Two-letter province or territory code (e.g. ON, QC, BC). Premium only.
`bank_name`	No	Bank name to search for. At least one of bank_name, city, province, or postal_code is required. Premium only.
`postal_code`	No	Postal code to search for branches. Premium only.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations only declare readOnlyHint=true, so the description carries most of the behavioral burden. It usefully discloses the premium subscription gate (an access constraint beyond the schema's per-param notes) but says nothing about result volume, pagination limits, or what the result set contains.

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?

Two sentences, zero filler, with the core capability front-loaded and the alternative plus access constraint following efficiently.

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?

With no output schema, the description's implied return (a list of branches with routing numbers) is adequate for the task, and the premium gate is surfaced. It stops short of describing result shape or pagination expectations that the offset parameter implies.

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%, including the premium-only flags and the 'at least one of bank_name, city, province, postal_code' requirement, so the schema does the heavy lifting. The description restates the same four filter dimensions but adds no format or syntax guidance beyond it.

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?

States a specific verb (finds) plus resource (Canadian bank branches and their routing numbers) and enumerates the four search dimensions. It also names the sibling it is not (the routing-number decoder) so an agent can route correctly without opening a schema.

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?

Explicitly routes the decode-a-known-number case to /canadaroutingnumber, which is the key alternative. It does not address narrower overlaps such as searchBanks or getBankInfo, but the primary use/not-use distinction is stated clearly.

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

All API Ninjas 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.

Resources

Need Help?