Skip to main content
Glama

Mark an enquiry

update_lead
DestructiveIdempotent

Sets the status of an enquiry to new, read, replied, done or archived. Mark an enquiry replied once the owner has answered it (this stops the follow-up reminder), and done when the job is finished: with Lead Autopilot, a review link saved on the site and an email address on the enquiry, marking it done sends that customer one review request from the business. Archived enquiries stay in the inbox until their retention period ends.

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>",
      "status": "<status>"
    },
    "name": "update_lead"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYes
lead_idYesThe enquiry id (starts with lead_) from list_leads.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds behavior the annotations cannot express: marking done can send a customer a review request under Lead Autopilot (a real external side effect), replied suppresses follow-up reminders, and archived keeps the enquiry in the inbox until its retention period. This does not conflict with the declared destructiveHint/idempotentHint and materially raises confidence in the mutation's consequences.

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?

Front-loads the operation, then spends the remainder on the payoff of each status. Dense but every clause carries information about side effects or retention; no filler sentences.

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, no-output-schema mutation, this gives the consequences of the risky transitions (email send, reminder suppression, retention) that an agent needs before acting. It omits transition rules (e.g. whether archived can be reversed) and failure behavior, which keeps it from a 5.

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 only 50%, and the description compensates by explaining what the status values mean in operational terms (replied, done, archived), while the schema documents lead_id as coming from list_leads. The new and read values go unexplained, leaving a small gap.

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?

Names a specific verb and resource ('Sets the status of an enquiry') and enumerates the full allowed value set: new, read, replied, done, archived. An agent can distinguish this from delete_lead, get_lead and list_leads without opening any schema.

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?

Gives concrete selection rules for the non-obvious values: replied once the owner has answered (stops the follow-up reminder), done when the job is finished. It does not name an alternative tool or state when not to use this one (e.g. when to delete instead), so it stops short of full routing guidance.

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