Skip to main content
Glama

Set the essence

set_outreach_essence
Idempotent

«Суть»: offer (what we offer), ask (what we want from the person), optional tone and client_rules, and the message language. [REST: PUT /api/tasks/{id}/outreach/essence]

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>",
      "offer": "<offer>",
      "ask": "<ask>"
    },
    "name": "set_outreach_essence"
  }
}

Input Schema

NameRequiredDescriptionDefault
askYes
toneNo
offerYes
task_idYesThe search id (task id), e.g. from list_searches or create_search.
languageNo
client_rulesNo
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

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only the HTTP verb PUT, which merely restates the idempotency hint, and says nothing about what happens to tone/client_rules when omitted on a repeat call — the most consequential unknown for an idempotent PUT-style write.

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 a single compact sentence with no filler, and the field enumeration is front-loaded. However, the untranslated '«Суть»' label and the bracketed REST endpoint note consume space without adding decision-relevant information for an agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a 7-parameter mutation with 29% schema coverage and no output schema, so the description should explain tone/client_rules semantics, overwrite behavior of optional fields, and the generation_id default. None of that is covered, leaving key calling decisions to inference.

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 only 29%, so the description must carry semantic weight. It does gloss two of the most important fields — offer ('what we offer') and ask ('what we want from the person') — which is genuine added meaning, but tone and client_rules are only labeled 'optional' with no semantics, and language is merely restated.

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 the object being set ('«Суть»') and enumerates the fields it consists of (offer, ask, tone, client_rules, language), plus the REST endpoint. But the verb is only implicit and the leading Russian term '«Суть»' is unexplained, so an agent must infer that this writes the outreach essence rather than merely reading it. It does not distinguish this from the sibling suggest_outreach_essence.

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 statement of when to call this versus suggest_outreach_essence or set_outreach_funnel, nor any prerequisite (e.g. does a generation need to exist first?). The only contextual hint is the REST path containing /tasks/{id}/outreach/essence, which an agent must decode itself.

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