Skip to main content
Glama

Price of retrying failed people

quote_outreach_retry

The price in credits of retrying the people whose messages failed, from where they stopped. Free; its credits is the confirm_credits of retry_outreach. [REST: POST /api/tasks/{id}/outreach/retry/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>"
    },
    "name": "quote_outreach_retry"
  }
}

Input Schema

NameRequiredDescriptionDefault
cidsNoThe failed people to retry; omitted: every failed person of the generation.
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.6/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and the description adds genuinely non-obvious context: the call itself is free of credit cost, and the returned `credits` feeds retry_outreach's confirm_credits. It does not explain why a quoting operation is marked non-read-only, whether a quote expires or must be consumed promptly, or whether repeated calls are counted — gaps that matter given idempotentHint=false.

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?

Two short sentences, front-loaded with the resource being priced, followed by the cost and the downstream contract. The trailing REST path is compact and the telegraphic "its `credits` is the confirm_credits of retry_outreach" carries real information rather than filler.

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?

With three fully documented parameters and no output schema, the description usefully names the response field (`credits`) and what to do with it, covering the main unknown an agent would face. What remains unstated is the rest of the response shape and quote validity, minor for a three-parameter pricing call.

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% and every parameter carries a clear description (cids, task_id, generation_id, including omission defaults), so baseline is 3. The description adds no additional meaning about the parameters — for instance, nothing about how cids interacts with the frozen price or scoping limits.

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 verb+resource: it returns the credit price of retrying only the people whose messages failed, resumed from where they stopped. This implicitly separates it from quote_outreach (full campaign quote) and retry_outreach (the actual execution), which it names by its confirm_credits contract. Sibling differentiation is present but indirect rather than stated outright.

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: the note that its `credits` value is the confirm_credits of retry_outreach tells the agent this is a prerequisite step for that call. There is no explicit "use this before X" statement and no exclusion guidance such as when to use quote_outreach instead for a whole-generation 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