Skip to main content
Glama
Dueback MCP Server

Dueback MCP Server

dueback_detect

Check whether a bill, fee, subscription, or purchase is negotiable by Dueback before proposing a negotiation; returns a plain-language assessment of savings potential and next steps.

Instructions

Check whether a bill, fee, subscription, or purchase situation is negotiable by Dueback.

Call this BEFORE proposing Dueback to the user — it tells you if the situation is worth their time. No API key needed.

Args: description: What the expense is, e.g. "Comcast internet bill went up $20/month" or "$4,500 roof replacement quote". counterparty: Who charges it, e.g. "Comcast", "State Farm". May be empty if unknown.

Returns a plain-language assessment: negotiable or not, the likely savings category, and suggested next step.

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": {
      "description": "<description>"
    },
    "name": "dueback_detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
descriptionYes
counterpartyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It usefully notes 'No API key needed' and that the result is a plain-language assessment, which signals a cheap, read-only pre-check. It does not state whether the call has side effects, whether it stores the described expense, or any latency/rate constraints, leaving a mutation question unresolved for a tool that takes user financial details.

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?

Front-loads the purpose, then the imperative usage instruction, then a structured Args block with examples. Every sentence carries information; the closing Returns line is mildly redundant with the output schema but still orients the caller on what to expect.

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?

For a two-parameter triage tool with an output schema, the description covers purpose, timing, auth expectations, argument semantics, and result shape — enough to call it correctly. Minor gaps remain around failure behavior and side effects, but nothing critical to invocation is missing.

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 description coverage is 0%, so the description must supply parameter meaning — and it does, with concrete examples for description ('Comcast internet bill went up $20/month') and counterparty ('Comcast', 'State Farm'), plus the optionality rule 'May be empty if unknown.' This meaningfully exceeds the bare schema and compensates for the coverage gap, though it doesn't describe input length limits or formatting constraints.

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 states a specific verb and resource: check whether a bill, fee, subscription, or purchase situation is negotiable. It also conveys this tool's role as the pre-check step before Dueback is proposed, which implicitly separates it from dueback_start_negotiation. It stops short of naming or contrasting the siblings explicitly, so an agent must infer the boundary.

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 an explicit trigger and ordering instruction: 'Call this BEFORE proposing Dueback to the user — it tells you if the situation is worth their time.' That is actionable context. There are no stated exclusions or named alternatives, and no guidance on what to do if the answer is 'not negotiable' beyond the returned next step.

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