Skip to main content
Glama

Deal Desk day plan

set_deal_desk_day
Idempotent

Sets today's Deal Desk budget and expected profit target (USD) for the active session. Pass null to clear one. 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": "set_deal_desk_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
budgetNoToday's buying budget in USD.
profitTargetNoToday's expected profit target in USD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this a non-destructive, idempotent, closed-world write (readOnlyHint=false), so the safety profile is covered. The description adds genuinely useful behavior: null clears a field, and alerts in the result must be surfaced to the user first. It stops short of saying what happens when no session is active or whether omitted fields are preserved.

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?

Three short sentences, front-loaded with the action and scope, then the null behavior, then the response-handling rule. Nothing is wasted or buried.

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 two-parameter idempotent write with no output schema, the definition covers purpose, null semantics, units, and the alert follow-up. The only gap is the precondition around an active session and whether unset fields are left untouched.

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% with min/max and USD units documented, so the baseline is 3. The description earns an extra point by explaining what the schema leaves ambiguous: passing null clears a value rather than erroring, which is non-obvious from the type union alone.

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?

States a specific verb ('Sets') and named resources ('today's Deal Desk budget and expected profit target') scoped to 'the active session'. An agent immediately knows what the tool writes, though it does not contrast itself with sibling settings/update tools.

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?

'For the active session' implies a session must already exist (open_deal_desk), and the alert-handling instruction gives a post-call behavior. However, there is no explicit when-to-use versus update_deal_desk_settings or end_deal_desk, and no stated precondition if no session is active.

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