Skip to main content
Glama

End Deal Desk

end_deal_desk
Idempotent

Ends the user's active Deal Desk session (when they say they are done for the show). It also closes itself after 24 hours with no activity. 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": "end_deal_desk"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With annotations already declaring destructiveHint=false, idempotentHint=true, and non-read-only, the description adds genuine context beyond them: the session self-terminates after 24 hours of inactivity, and any alerts in the result must be surfaced to the user first. It does not say whether session data is retained or discarded on an explicit end.

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, each carrying distinct information (what it does, the expiry behavior, the alert-handling obligation), with the core action front-loaded. No filler or repetition of the title.

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 zero-argument session-termination tool with no output schema, the description covers the action, the fallback expiry, and the one thing the agent must do with the result. It only lightly gestures at the result payload ("if the result has alerts") without indicating what else the response contains.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate at the argument level. Baseline 4 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?

States a specific verb and resource ("Ends the user's active Deal Desk session"), which is unambiguous against siblings like open_deal_desk and set_deal_desk_day. It does not explicitly name the counterpart tool to select instead, so it stops short of full sibling differentiation.

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?

"When they say they are done for the show" gives a concrete triggering condition an agent can act on, and the 24-hour auto-close tells the agent the session may already be gone. No when-not guidance or explicit alternative is given, but there is no real competing tool for ending a session.

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