Skip to main content
Glama

Price of an AI rewrite

quote_message_rewrite

The price in credits of rewriting one message by AI (mode). Free; answers result_id, expected_revision and credits for rewrite_message. [REST: POST /api/tasks/{id}/outreach/leads/{cid}/steps/{step_id}/rewrite/quote]

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>",
      "step_id": "<step_id>",
      "mode": "<mode>"
    },
    "name": "quote_message_rewrite"
  }
}

Input Schema

NameRequiredDescriptionDefault
cidYesThe person's id (cid) from list_leads.
modeYesother_hook (another fact), shorter, warmer, rewrite (with the note).
step_idYesThe step id of the message (get_outreach_lead steps[].step_id).
task_idYesThe search id (task id), e.g. from list_searches or create_search.
generation_idNoThe outreach generation id (get_outreach campaign.generation.id); omitted: the current one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare a non-read-only, non-destructive, non-idempotent, closed-world call; the description adds the materially useful fact that the operation is 'Free', so no credits are consumed by quoting. Because there is no output schema, the description also carries the return contract by naming result_id, expected_revision and `credits`, which is exactly what is needed to chain into rewrite_message. The REST path is a bonus for debugging but adds little for an agent.

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?

Three compact clauses with the core purpose front-loaded, so an agent gets the gist from the first phrase. The middle clause is telegraphic ('Free; answers ...') and slightly awkward to parse, and the bracketed REST path is low-value for tool selection but does not obscure the main claim.

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 five-parameter, no-output-schema tool, the definition covers purpose, cost behavior, and the three fields the caller must retain for the follow-up call, and the schema fully documents every parameter. The main remaining gap is the relationship between `expected_revision` and the subsequent rewrite call, which is named but never explained.

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 100%, including enum values for `mode` and the optional `generation_id`, so the schema already does the explanatory work. The description mentions `mode` only parenthetically as '(mode)' without adding meaning about how each mode affects the quoted price. Baseline 3 is appropriate here.

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?

States a specific resource and quantity: the credit price of an AI rewrite of one message, parameterized by `mode`. It also names `rewrite_message` as the operation it prices, which separates it from generic quoting siblings. It does not, however, explicitly contrast itself with the other quote_* tools (quote_outreach, quote_outreach_retry, quote_search).

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 implied rather than stated: by saying it 'answers result_id, expected_revision and `credits` for rewrite_message', the reader can infer this is a pre-flight check to call before the actual rewrite. There is no explicit 'call this before rewrite_message' instruction, no statement of when to skip it, and no note about the consequence of calling rewrite_message without a prior quote.

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