Skip to main content
Glama
Sign In

Lower My Bill

by io.github.GoodTurnStudio
OverviewDiscussionsAdmin

Calendar reminder to call before a deal ends

get_call_reminder
Read-onlyIdempotent

Calendar reminder to call before a deal ends. Needs deal_ends plus bill, provider or both. Returns a calendar file (.ics) with an all-day event about 30 days before the deal ends, holding the full script, offers to ask for and a confirm-in-writing message, with alerts at 9am the day before and on the day. Nothing is stored. get_bill_script gives this link as add_to_calendar when deal_ends is given.

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": {
      "deal_ends": "<deal_ends>"
    },
    "name": "get_call_reminder"
  }
}

Input Schema

NameRequiredDescriptionDefault
billNoBill type, as for get_bill_script. Give bill, provider or both.
countryNoTwo-letter country code. GB (or UK) gives the UK script when no provider is named. Defaults to the caller's country, else US.
providerNoCompany name, as for get_bill_script.
deal_endsYesThe date the current price or policy ends, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / bill / description
      Previous value: -"Bill type, as for getBillScript. Give bill, provider or both."New value: +"Bill type, as for get_bill_script. Give bill, provider or both."
    • changedInput schema / properties / provider / description
      Previous value: -"Company name, as for getBillScript."New value: +"Company name, as for get_bill_script."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Despite annotations already declaring readOnly/idempotent/non-destructive, the description adds substantial behavior: what gets generated (full script, offers to ask for, confirm-in-writing message), the event timing (~30 days before, alerts at 9am day-before and day-of), and the explicit 'Nothing is stored' state guarantee. This is exactly the context annotations cannot convey.

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?

Sentences are front-loaded (purpose, prerequisites, return contents, then the sibling link) with no filler. Every clause — event timing, embedded content, storage guarantee, cross-reference — carries actionable information an agent would otherwise have to guess.

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?

For a 4-param tool with no output schema, the description covers purpose, required inputs, returned file content and format, timing, and the sibling relationship. Nothing an agent needs to call it correctly is missing.

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 coverage is 100%, so the schema already documents deal_ends, bill, provider, and the country default. The description's 'Needs deal_ends plus bill, provider or both' largely restates the schema's own guidance rather than adding new semantics, so the baseline 3 applies.

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 first sentence states a specific verb+resource: a calendar reminder to call before a deal ends. It names the exact output (.ics file with all-day event) and how it relates to the sibling get_bill_script, so an agent can distinguish it 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?

It gives a clear prerequisite ('Needs deal_ends plus bill, provider or both') and explains the sibling relationship: get_bill_script surfaces this link as add_to_calendar when deal_ends is present. It stops short of naming an explicit when-not or an alternative to pick instead, so it lacks the full routing guidance of a 5.

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

All Lower My Bill toolsInspect
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