Skip to main content
Glama

Record a name drop

record_name_drop
Idempotent

Record what happened to a name-drop lead from get_name_drop_leads.

Call it as soon as the rep sends the message (outcome "sent") or decides not to (outcome "skipped"). A lead nobody reports on stays reserved for the rep for weeks, so skipping matters: it frees the prospect for a teammate.

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>",
      "outcome": "<outcome>"
    },
    "name": "record_name_drop"
  }
}

Input Schema

NameRequiredDescriptionDefault
lead_idYesThe lead's lead_id, exactly as get_name_drop_leads returned it.
outcomeYes"sent" or "skipped".
skip_reasonNoOnly with "skipped", when there is a reason: "already_talking" (we are already in touch with them), "not_a_fit" (wrong person or account), "bad_path" (they don't really know the connector; never pair these two again). Leave it out to just pass.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare the write/idempotent/non-destructive profile, so the bar is lower. The description adds genuinely non-obvious domain behavior: an unreported lead stays reserved for the rep for weeks, and reporting a skip frees the prospect for a teammate. It does not mention what a repeat call returns or how the response signals success, but idempotency is already covered by annotations.

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, front-loaded sentences: what it does, when to call it, and why it matters. No restated field documentation, no boilerplate, and the consequence sentence earns its place by motivating the "skipped" path.

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?

An output schema exists so return values need not be described, parameters are fully documented in the schema, and the description covers purpose, timing, and behavioral consequence for a simple 3-parameter write tool. Nothing an agent needs to invoke it correctly is missing.

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% and the parameter descriptions already define lead_id provenance and the full skip_reason vocabulary including "bad_path" (never pair again). The description adds nothing about individual parameter semantics beyond the outcome values echoed in the schema, so this sits at the baseline with only slight reinforcement from the usage sentence.

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?

States a specific verb and resource ("Record what happened to a name-drop lead") and anchors the resource to its source tool, get_name_drop_leads, so the agent knows this is the write-back counterpart to that read tool. It is immediately distinguishable from the sibling that produced the lead.

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?

Gives explicit triggering conditions with timing ("as soon as the rep sends the message" for outcome "sent" or "decides not to" for "skipped") and explains the cost of not calling it. The negative case (skipping) is called out as consequential rather than optional, which is exactly the guidance an agent needs.

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