Skip to main content
Glama

A line to say at the dealership

desk_script
Read-onlyIdempotent

A short line a buyer can say at a moment in the dealership's sales or finance office, such as being asked for a monthly payment, a credit check before a price, or a pitch for an add-on, with when it applies and why it works. Use it when someone describes what's happening at the desk. Pass a script id (monthly-payment, trade-first, down-payment, credit-check, numbers-changed, preinstalled-add-ons, initial-worksheet, decide-today, beat-my-rate, fi-product, only-a-month, paint-or-markup, below-invoice, trade-below-offer, leaving) or a short description; returns the one or two lines that fit, or the list of situations on file when none does.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "situation": "<situation>"
    },
    "name": "desk_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
situationYesA script id or a short description, like "they keep asking my monthly payment"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuine behavioral value by disclosing the fallback: when nothing matches it returns the list of situations on file rather than erroring, which an agent needs to interpret a non-answer.

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?

Two sentences, front-loaded with the purpose before the mechanics, and every clause carries information. The long parenthetical list of ids is dense but necessary given the schema lacks an enum, though it slightly bloats the read.

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 does the work of explaining returns (the fitting line(s) or the list of situations on file), and it covers the input domain fully. Only minor gaps remain, such as whether the response indicates which situation matched.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema only says "a script id or a short description," but the description enumerates all fifteen accepted script ids (monthly-payment, trade-first, beat-my-rate, etc.), which appear nowhere in the schema since no enum is defined. This is meaningful semantics added beyond structured data.

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?

The description states a concrete resource and outcome: it returns one or two lines a buyer can say at a specific dealership sales/finance moment, with three example moments named. It is clearly distinguishable from siblings like dealer_email or check_quote, though it never explicitly contrasts itself with them.

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?

"Use it when someone describes what's happening at the desk" gives a clear triggering condition, and the enumerated moments (monthly payment ask, credit check before price, add-on pitch) reinforce it. No explicit when-not-to-use or alternative routing is provided, so it falls short of a 5.

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