Skip to main content
Glama

Draft the offer

suggest_outreach_essence

A draft of «Что предлагаем» (the offer) from the search's onboarding. Free for the user (it may spend the generation's brief). [REST: POST /api/tasks/{id}/outreach/essence/suggest]

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": "suggest_outreach_essence"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesThe search id (task id), e.g. from list_searches or create_search.

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 already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful non-schema context – the call is free to the user but may consume the generation's brief – which explains the non-idempotent hint. It stops short of saying whether the draft is persisted or merely returned, or what a repeat call costs.

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?

Two tight sentences plus a REST endpoint tag; the artifact and the cost note are both front-loaded and nothing is padded. The noun-phrase opening is slightly less direct than the title 'Draft the offer', a minor structural weakness.

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 one-parameter generation tool this covers what is produced and what it costs. It omits whether the draft is applied or only returned, what the response contains (no output schema exists to compensate), and its relationship to set_outreach_essence, leaving real gaps for an agent deciding how to proceed after the 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?

With a single parameter at 100% schema description coverage (including a pointer to list_searches/create_search as the source of the id), the schema already carries the semantics. The description adds nothing about task_id, so the baseline 3 applies.

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 identifies the exact artifact produced – a draft of «Что предлагаем» (the offer) drawn from the search's onboarding – which is specific enough to distinguish it from set_outreach_essence, since this generates rather than assigns. It is phrased as a noun phrase ('A draft of...') rather than an explicit verb, and never names the sibling it contrasts with, so it falls short of a 5.

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

Usage Guidelines4/5

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

Implicit context is clear: use it to obtain a draft offer before committing one with set_outreach_essence. There are no explicit exclusions or prerequisites ('when not to use', whether a search must be onboarded first), so it lands at 4 rather than 5.

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