Skip to main content
Glama

Pass on a deal

pass_deal
Idempotent

Marks one of the user's Deal Desk checks as passed (the user walked away). dealId comes from check_deal or check_trade. If the result has alerts, show them to the user before anything else.

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": {
      "dealId": "<dealId>"
    },
    "name": "pass_deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
dealIdYesThe dealId from check_deal or check_trade.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context that a result may contain alerts requiring user-facing display, but it does not say what a successful pass returns or whether the pass can be reversed or re-checked.

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?

Two tight sentences with no filler; the action is front-loaded and the argument source and alert-handling rule follow in order of relevance. Every sentence carries information an agent needs.

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 single-parameter, non-destructive, idempotent mutation with no output schema, the definition covers purpose, argument provenance, and the one non-obvious response behavior (alerts). It is only slightly incomplete in not describing the success response shape or error conditions.

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?

With one parameter at 100% schema description coverage, the schema already documents dealId and even names its source. The description restates that provenance rather than adding new meaning such as validation rules or behavior for an invalid/stale dealId, so the baseline of 3 applies.

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 gives a specific verb and resource ("Marks one of the user's Deal Desk checks as passed") and glosses the domain term with "the user walked away," so the agent knows exactly what state change occurs. It ties itself to the check_deal/check_trade workflow, which differentiates it from unrelated siblings, though it does not explicitly contrast with any sibling that performs a non-passing outcome.

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 states the precondition for the required argument (dealId comes from check_deal or check_trade) and gives an ordering instruction (show alerts before anything else). It stops short of explicit when-not guidance, e.g. what to do if the check has unresolved alerts or if the deal was never checked.

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