Skip to main content
Glama

DentalCostFinder Canada MCP

check_cdcp_coverage

Check Canadian Dental Care Plan (CDCP) eligibility, co-payment tier by adjusted family net income, and covered dental services.

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": {
      "adjustedFamilyNetIncome": "<adjustedFamilyNetIncome>"
    },
    "name": "check_cdcp_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
hasPrivateInsuranceNoWhether the applicant has access to private or employer dental insurance.
isCanadianTaxResidentNoWhether the applicant is a Canadian resident for tax purposes and filed a return.
adjustedFamilyNetIncomeYesAdjusted family net income in CAD from the latest CRA tax return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses what the tool computes, and "Check" implies a non-mutating lookup, but it says nothing about whether the result is advisory vs. authoritative, regional/program-year constraints, or what happens when optional inputs like hasPrivateInsurance are omitted.

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?

A single front-loaded sentence with no filler; the three deliverables are enumerated compactly. It is dense but every clause carries information, and nothing needs trimming.

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

Completeness3/5

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

With no output schema and no annotations, the description must stand in for return-value documentation; it names the three outputs but not their shapes (boolean vs. tier value vs. service list), so an agent knows what it gets conceptually but not structurally.

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 defines all three parameters, establishing a baseline of 3. The description adds one useful tie-in — that adjusted family net income drives the co-payment tier — but does not explain how hasPrivateInsurance or isCanadianTaxResident affect the eligibility outcome.

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 concrete verb ("Check") and names the specific resource and three outputs: CDCP eligibility, co-payment tier, and covered services. It is clearly distinguishable from the cost-estimation and procedure-listing siblings, though it never names them 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 only implied: an agent can infer this is the eligibility/screening step that precedes estimate_dental_procedure_cost, but the description states no when-to-use condition, no prerequisites (e.g., must check eligibility before estimating), and no exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources