Skip to main content
Glama
Dueback MCP Server

Dueback MCP Server

dueback_case_status

Check a Dueback negotiation case's status by case ID and retrieve the counterparty, current stage, and recorded savings or fee.

Instructions

Check the status of a Dueback negotiation case.

Args: case_id: The case ID returned by dueback_start_negotiation.

Returns the case status (e.g. strategy_loop, verifying, closed), the counterparty, and any recorded savings/fee. Requires DUEBACK_API_KEY in the server environment.

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": {
      "case_id": "<case_id>"
    },
    "name": "dueback_case_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
case_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It states the DUEBACK_API_KEY requirement and summarizes returned fields, but it does not explicitly confirm read-only/idempotent behavior, rate limits, or error handling.

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 purpose and structured into Args and Returns sections with no rambling. The Returns block partly duplicates the existing output schema, but it remains compact and scannable.

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 one-parameter status lookup with an output schema, the description covers purpose, parameter origin, return categories, and API key requirement. It leaves some guidance gaps around alternatives and read-only behavior, but it is largely complete for this complexity.

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?

The single case_id parameter has 0% schema description coverage, and the description adds meaningful provenance by saying it is the case ID returned by dueback_start_negotiation. It does not add format details, but the provenance is the key semantic an agent needs.

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 the status of a Dueback negotiation case.' It also ties case_id to dueback_start_negotiation, but it does not explicitly distinguish itself from sibling dueback_detect, so it is clear without full sibling differentiation.

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?

The description implies this should be called after dueback_start_negotiation because case_id is described as the ID returned by that tool, giving a usage precondition. However, it does not explicitly say when to use this versus dueback_detect or when not to use it.

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