Skip to main content
Glama

Price of the outreach

quote_outreach

The price in credits of researching and writing messages for the chosen fit people (per person, total, the most it may hold), the balance, and who is skipped. Free. Its credits is the confirm_credits of start_outreach. [REST: POST /api/tasks/{id}/outreach/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>",
      "cids": "<cids>"
    },
    "name": "quote_outreach"
  }
}

Input Schema

NameRequiredDescriptionDefault
cidsYesFit people (cid) of the search; get_outreach lists them.
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?

Beyond the annotations, the description discloses that the call is 'Free' (no credits consumed), what the response contains including a 'skipped' set, and that the `credits` value is the exact confirm_credits to feed into start_outreach — valuable behavioral context. readOnlyHint=false is consistent with the disclosed POST endpoint, so no contradiction. It does not explain why people are skipped or whether a quote is cached/expires, which keeps it from a 5.

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?

Very compact — one dense sentence plus two short fragments ('Free.' and the REST path). The scoping ('per person, total, the most it may hold') is front-loaded and each element earns its place. The parenthetical stack and the sentence fragment make it slightly choppy, but there is no 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 no output schema, the description does the work of describing the return payload (per-person, total, cap, balance, skipped) and its cost-free nature. It also explains the hand-off value to start_outreach. It leaves somewhat vague what the 'skipped' list means and when it is non-empty, but for a three-parameter quote call it is largely complete.

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%, so all three parameters are already documented in the schema, including generation_id. The description only restates the cids concept as 'the chosen fit people' and adds nothing about generation_id or the 300-item cap. Baseline 3 is appropriate when the schema carries the meaning.

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 states precisely what is priced — 'researching and writing messages for the chosen fit people' — and enumerates the returned figures (per person, total, maximum hold, balance, skipped). It also distinguishes itself from start_outreach by naming the link ('Its `credits` is the confirm_credits of start_outreach'). The only weakness is that the purpose is phrased as a noun phrase ('The price in credits of...') rather than an explicit verb, so the agent must infer 'quote/estimate before starting'.

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: 'Free' plus the confirm_credits link to start_outreach signals this is a pre-flight cost check. However, there is no explicit 'call this before start_outreach' instruction, and no mention of when to prefer quote_outreach_retry or how it relates to other quote_* siblings. The agent can infer the workflow but is not told it.

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