Skip to main content
Glama

An AI variant not applied

get_message_variant
Read-onlyIdempotent

A finished AI variant of a person's messages that was not applied because the text was edited meanwhile (its id from get_outreach_lead). [REST: GET /api/tasks/{id}/outreach/leads/{cid}/candidates/{candidate_id}]

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": "get_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.
candidate_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: the returned variant is a stale artifact preserved because the message text was edited concurrently, which tells the agent the data may no longer match the live message. It stops short of describing any response shape or pagination, so a 3 is appropriate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is compact and front-loads the resource meaning, but the body is an ungrammatical sentence fragment and the bracketed REST endpoint consumes roughly a third of the text with information mostly redundant with the schema path. It earns most, but not all, of its length.

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?

With three required parameters, no output schema, and an entity that clearly holds message content, the description should indicate what a 'variant' contains (text, tone, length, timestamps) since no output schema documents it. It conveys the state and origin of the record but not what the agent will actually receive, leaving a meaningful gap for a tool with no output schema.

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 67%; cid and task_id are documented in the schema, but candidate_id has no schema description at all. The description partially compensates by stating the candidate id originates from get_outreach_lead, and the REST path maps id→task_id, cid→lead, and candidate_id→candidate. That is helpful but thin for the one undocumented parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource — a finished AI variant that was not applied — and gives the reason it was never applied, which distinguishes it from apply_message_variant. However, it is a bare noun phrase with no verb, so it never actually states that the tool retrieves/fetches that variant; the agent infers the action from the tool name alone.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative (e.g. apply_message_variant or get_outreach_lead). The only operational hint is the parenthetical that candidate_id comes from get_outreach_lead, which is provenance for one parameter rather than usage 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