Skip to main content
Glama

Deal Desk settings

update_deal_desk_settings
Idempotent

Changes the user's Deal Desk profit settings and/or confirms them for this session. minProfit (USD, null = none), minRoiPct (0–200, default 10), feePct (selling fee %, 0–50, default 13.25), orderFee (USD per order, default 0.40), shipping (USD shipping & supplies, default 5), offerPct (opening offer as % of max buy, 50–100, default 90). Pass confirmFees true once the user has confirmed the selling costs shown by open_deal_desk. If the result has alerts, show them to the user before anything else.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_deal_desk_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
feePctNoSelling fee percent.
offerPctNoOpening offer as a percent of max buy.
orderFeeNoPer-order fee in USD.
shippingNoShipping & supplies per sale in USD.
minProfitNoMinimum net profit per deal in USD; null removes it.
minRoiPctNoMinimum ROI percent (5, 10, 15, 20 or custom).
confirmFeesNoTrue when the user confirmed the selling costs for this session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the description's job is to add context, and it does: it discloses default values the schema omits, states that null removes minProfit, and specifies post-call behavior for alerts. It does not say whether calling without confirmation is an error or whether unlisted settings are preserved, which would have pushed this higher.

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 purpose is front-loaded in the first sentence and the conditional instructions come last, which matches call order. The dense inline parameter run-on is efficient but harder to scan than a short list, and it repeats ranges the schema already enforces.

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 7-parameter mutation tool with no output schema, the definition covers defaults, null semantics, the confirmation gate, and alert handling — enough to call it correctly. The remaining gap is the return shape beyond 'alerts' and what happens if confirmFees is never passed.

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 coverage is 100%, so the baseline is 3, but the description earns an extra point by supplying defaults (minRoiPct 10, feePct 13.25, orderFee 0.40, shipping 5, offerPct 90) and units that the schema does not declare anywhere. The inline parenthetical for each field also restates ranges already in the schema, so some of the text is redundant.

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 names a specific verb and resource ('Changes the user's Deal Desk profit settings') and captures the dual mode ('and/or confirms them for this session'), which is not obvious from the name alone. It also ties the confirm path to the sibling open_deal_desk, so an agent can place this tool in the workflow without opening the 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 an explicit sequencing rule: pass confirmFees true only after the user has confirmed the selling costs shown by open_deal_desk, plus a post-call instruction to surface alerts first. It stops short of saying when not to call it (e.g., when only the session day is being changed via set_deal_desk_day), so the routing guidance is clear but not exhaustive.

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