Skip to main content
Glama

Apply an AI variant

apply_message_variant

Replaces the person's messages with that variant (free); result_id and expected_result_revision from get_outreach_lead. [REST: POST /api/tasks/{id}/outreach/leads/{cid}/candidates/{candidate_id}/apply]

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": {
      "task_id": "<task_id>",
      "cid": "<cid>",
      "candidate_id": "<candidate_id>"
    },
    "name": "apply_message_variant"
  }
}

Input Schema

NameRequiredDescriptionDefault
cidYesThe person's id (cid) from list_leads.
task_idYesThe search id (task id), e.g. from list_searches or create_search.
result_idNo
candidate_idYes
expected_result_revisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-idempotent, non-destructive mutation, so the bar is lower. The description adds two genuinely new facts beyond annotations: the operation replaces existing messages, and it is free. It does not explain what happens on a revision mismatch, whether the replacement is reversible, or any concurrency implication of expected_result_revision.

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?

The effect is front-loaded in the first clause, followed by the parameter-origin hint and a REST breadcrumb. It is tight and wastes no sentences, though the ordering of effect, cost note, and param source is slightly crammed into one line.

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

Completeness3/5

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

For a five-parameter mutation with 40% schema coverage and no output schema, the description covers the core effect, cost, and two of the five parameters. It leaves out failure behavior (revision conflict), the meaning of candidate_id's source tool, and whether the prior message text is retrievable, so it is adequate but not sufficient.

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 description coverage is 40%, so the description must compensate and it only partly does: it documents the source of result_id and expected_result_revision (get_outreach_lead) and links candidate_id to 'that variant'. It never explains what expected_result_revision actually guards against (optimistic concurrency) or where candidate_id comes from, leaving two parameters weakly described.

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 names a specific verb and effect: it 'replaces the person's messages with that variant', which is clearly distinct from the read-only siblings like get_message_variant or get_outreach_lead. The phrase 'that variant' is slightly under-specified (it relies on candidate_id being a variant id), so it falls short of a perfect 5.

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?

Usage is only implied: you fetch a variant, then apply it. The description helpfully says where result_id and expected_result_revision come from (get_outreach_lead), but it never states when to apply a variant versus rewriting (rewrite_message) or quoting a rewrite (quote_message_rewrite), and gives no preconditions or exclusions.

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