Skip to main content
Glama

Rebate check

rebate_check
Read-onlyIdempotent

Satellite rebate status for every province and territory, plus the federal Connecting Families Initiative. Status is open, ended, paused, unverified, or none found, with the amount, window, official link, and checked date. Phoenix cannot decide eligibility. Read only.

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": {
      "province": "<province>"
    },
    "name": "rebate_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
provinceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world behavior. The description adds useful behavioral context beyond that: the possible statuses, the returned fields including amount, window, official link, and checked date, plus the important caveat that Phoenix cannot decide eligibility.

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?

The description is front-loaded with the core purpose and stays compact across three sentences. 'Read only' is redundant with the annotations, but otherwise every sentence adds useful information.

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?

For a simple read-only lookup with no output schema, the description does a good job enumerating return fields and status values. However, it leaves the sole input parameter underspecified and does not resolve how to request federal-initiative results, which is a meaningful completeness gap.

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

Parameters2/5

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

The only parameter is 'province', and schema description coverage is 0%. The description does not explain accepted province formats or values, and it is ambiguous how the required province parameter should be used to retrieve the federal Connecting Families Initiative result.

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?

The description clearly states that this returns satellite rebate status by province/territory and for the federal Connecting Families Initiative, including the status categories and returned fields. It is specific about the resource and output, but it does not explicitly distinguish itself from sibling offer tools such as content_offers or local_offer.

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: use it to look up rebate status for a province or territory. The line 'Phoenix cannot decide eligibility' usefully bounds the tool away from eligibility determination, but there is no explicit guidance on when to choose this versus related offer tools.

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