Skip to main content
Glama

Deal Desk scoreboard

deal_desk_scoreboard
Idempotent

The user's Deal Desk numbers for a period (24H, 7D, MTH or YTD; default 7D) and one show session or all: cards checked, bought, passed, traded, listed and sold; actual cash (spent, sales, fees, cash profit) kept apart from estimates (trade value, expected profit on unsold cards); unsold inventory at cost, average ROI, profit per $1,000 spent, sell-through, capital turnover, speed and aging, plus today's budget left. Say which numbers are actual cash and which are estimates, as labelled. 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": "deal_desk_scoreboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNoDefault 7D.
sessionNoA session id from the sessions list, or "all" (default).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only cover the safety profile (idempotent, non-destructive, openWorld=false) and add little about the payload, so the description usefully discloses what the return actually contains and how to present it — separating actual cash (spent, sales, fees, cash profit) from estimates (trade value, expected profit on unsold cards), and prioritizing alerts before other output. It does not explain what constitutes an 'alert' or whether data depends on an active session, which is why this is not a 5.

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?

Purpose and defaults are front-loaded in the first clause, and the semicolon-separated metric groups are dense but earn their place given there is no output schema to document returns. The enumeration is longer than ideal, but the final two sentences (labelling cash vs estimates, surfacing alerts first) are actionable instructions rather than filler.

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?

With no output schema, the description carries the burden of describing return values and does so thoroughly, including the cash-vs-estimate distinction that would otherwise be ambiguous. The remaining gap is context: it never states prerequisites (an open/active Deal Desk, logged show sessions) or what triggers the alerts it tells the agent to surface.

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 coverage is 100%, so both parameters are already documented, and the description largely restates them (period values 24H/7D/MTH/YTD, default 7D; session id or 'all'). It adds marginal value by clarifying that 'session' means one show session, but supplies no format or selection advice beyond the schema.

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 resource ('the user's Deal Desk numbers') with a defined scope (period + session) and enumerates exactly what it returns: cards checked/bought/passed/traded/listed/sold, cash vs estimate figures, inventory, ROI, sell-through, aging, budget left. An agent can tell this is a read of a performance scoreboard, not a per-item listing tool like my_sales or an action tool like check_deal.

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?

Usage is only implied: it documents the period default (7D) and the session default ('all'), and gives a presentation rule for alerts, but never says when to reach for this tool versus siblings such as my_sales or collection_movers, nor whether an open Deal Desk session is required. An agent can infer intent but gets no explicit alternative routing or exclusions.

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