Skip to main content
Glama
Sign In

Emailchaser

by com.emailchaser
OverviewDiscussionsAdmin

Update lead category

update_lead_category
Idempotent

Sets or corrects a lead's category (tag), typically to fix an AI misclassification of a reply. Setting meeting_booked behaves exactly like marking a meeting as booked. Changing the category away from meeting_booked does NOT clear the booked-meeting mark: that mark is removed only by unmarking the meeting. A real change fires the LeadCategoryUpdate webhook; setting the value the lead already has is a no-op.

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": {
      "id": "<id>",
      "category": "<category>"
    },
    "name": "update_lead_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe numeric lead ID (returned when the lead was created)
categoryYesThe category to set

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description discloses that a real change fires the LeadCategoryUpdate webhook, that setting an identical value is a no-op, and that the meeting_booked value has a coupled side effect on the booked-meeting mark. These are non-obvious behavioral traits an agent could not infer from structured fields alone.

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 tight sentences with zero filler: purpose first, then the coupled-value behavior, then the side-effect and webhook/no-op rules. Each sentence carries distinct, actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation with a fully documented schema and no output schema, the description covers everything needed: what it changes, the special enum value, the non-obvious side effect, the webhook emission, and idempotent no-op behavior.

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%, so both parameters are already documented and a baseline of 3 applies. The description goes further by explaining the special semantics of the meeting_booked enum value and its interaction with the booked-meeting mark, adding meaning the enum list alone does not convey.

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?

The description opens with a specific verb and resource ('Sets or corrects a lead's category (tag)') and immediately narrows the scope to correcting an AI misclassification. It is distinguishable from update_lead (field-level edits) and mark_lead_meeting/unmark_lead_meeting, whose behavior it explicitly separates out.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the primary reason to use the tool (fixing a misclassified reply) and explicitly says the booked-meeting mark is removed only by unmarking the meeting, which routes the agent to unmark_lead_meeting instead of clearing it here. The no-op case is also called out, so the agent knows when the call is unnecessary.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Emailchaser toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources