Skip to main content
Glama

Open Deal Desk

open_deal_desk
Idempotent

Starts or resumes the user's SlabLineage Deal Desk session (call it when the user says "Open SlabLineage Deal Desk", "open Deal Desk" or wants to check deals at a card show). Returns the session, the profit settings and today's budget. While feesConfirmed is false (a new session), before checking any deal show the user the confirmFees line and ask them to confirm or change it, then call update_deal_desk_settings with confirmFees true (and any changes). Deal Desk needs SlabLineage Pro. 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": "open_deal_desk"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional session name, e.g. "Denver Card Show".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing what is returned (session, profit settings, today's budget), the feesConfirmed prerequisite with the exact field to surface, the SlabLineage Pro entitlement requirement, and the rule to show alerts first. Annotations only say this is a non-destructive, idempotent write; the description supplies the operational contract.

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?

Front-loads purpose and trigger phrases, then the conditional fee-confirmation workflow, then the Pro requirement and alert rule in descending priority. It is dense but nearly every sentence carries a distinct obligation; the return-value sentence is the only part that could be trimmed.

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?

Covers the calling triggers, the gated setup flow, the entitlement prerequisite, and the ordering of alert display for a mutation tool with one optional parameter and no output schema. Nothing an agent needs in order to call it and act on the result 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 description coverage is 100% for the single optional `name` parameter, so the schema already carries the semantics and the baseline is 3. The description never mentions `name` or what a session name affects, so it adds nothing on top of the structured field.

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?

States a specific verb and resource ("Starts or resumes the user's SlabLineage Deal Desk session") and lists the exact utterances that trigger it. It also separates it from siblings by naming update_deal_desk_settings as the follow-up tool, so an agent can route correctly without opening other schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use triggers ("Open SlabLineage Deal Desk", "open Deal Desk", checking deals at a card show) and a conditional gate: on a new session with feesConfirmed false, confirm fees before checking any deal. It names the alternative tool and the state condition that selects it.

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