opportunity-exchange

get_rents

Measured rental markets (CMHC Rental Market Survey via Statistics Canada, real data): average rents by unit type (bachelor to 3+ bedroom) and rental vacancy rates for every surveyed centre in Canada, October survey. Pass province for one province’s centres, centre (cmhcCode) for one centre, neither for the national overview. Suppressed cells are null and unsurveyed centres absent — never zero.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`centre`	No	CMHC/StatCan geography code (cmhcCode) from a previous get_rents call.
`province`	No	SGC 2021 code or postal abbreviation (e.g. SK).

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description covers behavioral traits: suppressed cells are null, unsurveyed centres absent, and data is from October survey. It does not mention auth or rate limits but discloses data quirks.

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 sentences, front-loaded with the main purpose and key details. Every sentence adds value with zero redundancy.

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?

Given no output schema, the description fully explains what is returned (rents, vacancy rates, null handling) and covers edge cases (suppressed, absent centres). Complete for a simple two-parameter tool.

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 coverage is 100% with descriptions for both parameters. The description adds context beyond schema by explaining the three usage modes (province, centre, neither) and the meaning of cmhcCode.

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 it provides average rents by unit type and vacancy rates for Canadian rental markets, sourced from CMHC/StatCan. It distinguishes from sibling tools like get_real_estate by specifying the data source and scope.

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 explains when to use province, centre, or neither for national overview. However, it does not explicitly state when not to use this tool or mention alternative tools for filtering.

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

All opportunity-exchange tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0

Disambiguation1/5

Several tools are effectively duplicates or near-duplicates: get_emerging_signals is an explicit alias for list_economic_signals, resolve_entity and resolve_entities overlap heavily, and the markdown variants duplicate their non-markdown reports. Pairs like compare_communities/compare_municipalities and search_businesses/search_licensed_businesses also require reading long contracts to avoid misselection.

Naming Consistency4/5

Tool names overwhelmingly follow a snake_case verb_noun pattern with sensible verbs like get_, list_, search_, and compare_. The main deviations are the backwards-compatible get_emerging_signals alias and prefix choices such as check_business_health vs get_business_health that obscure the underlying distinction.

Tool Count1/5

70 tools is an extreme surface for any MCP server, far beyond the 25+ 'too many' threshold. The set is fragmented by format variants, aliases, and multiple overlapping lookup tools, making selection and maintenance costly.

Completeness3/5

The domain surface is broad: entity resolution, business health, labour, community economy, procurement, and governance evidence are all covered in depth. However, there are notable lifecycle gaps—no sandbox deletion, consent revocation, health-action cancellation, or actual exchange/connect/apply step—that leave agents with dead ends.

Resources

Need Help?