Skip to main content
Glama

Get Lead Delivery & Billing Status (Dealer-Authenticated)

get_lead_status

Check the delivery state, webhook/email attempts, duplicate flag, and billing ledger status of a submitted lead. Requires dealer_api_key.

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": {
      "lead_id": "<lead_id>",
      "dealer_api_key": "<dealer_api_key>"
    },
    "name": "get_lead_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
lead_idYesThe unique lead ID returned by submit_lead.
dealer_api_keyYesDealer API key for authentication.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose useful traits: the auth requirement (dealer_api_key) and the specific data classes returned. It stops short of noting error behavior for unknown lead IDs, retry semantics, or whether the call is purely read-only in effect.

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?

Two tight sentences; the functional scope is front-loaded and the auth prerequisite follows. No 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?

No output schema exists, so the enumerated return facets (delivery state, attempts, duplicate flag, billing ledger) are exactly what the description needed to supply, and the auth prerequisite is stated. Only failure-mode behavior is unaddressed.

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, including the lead_id linkage to submit_lead. The description only restates the auth requirement ('Requires dealer_api_key') and adds no format or constraint detail beyond the schema.

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 (check) and resource (status of a submitted lead) and enumerates the exact facets inspected: delivery state, webhook/email attempts, duplicate flag, billing ledger. This clearly separates it from siblings like get_vehicle, search_inventory, and submit_lead, though it never names a sibling explicitly.

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?

'of a submitted lead' implies this is called after submit_lead, giving weak contextual guidance. There is no explicit when-to-use/when-not-to-use statement, no mention of what to do if the lead is missing, and no named alternatives.

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