Skip to main content
Glama

Suggest outreach goals (onboarding step 2)

suggest_goals

Step 2 («Цель»): four goals for the outreach to the people found (e.g. invite to a call), from the company description. The user picks or writes one. Part of a new search's onboarding: the first assistant call of an onboarding spends one brief (a free account has one search brief and may call each assistant once); pass the returned onboarding_id to the next calls and to create_search. [REST: POST /api/assist/goals]

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": {
      "company": "<company>"
    },
    "name": "suggest_goals"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesThe company description (step 1).
onboarding_idNoThe onboarding id that ties the assistant calls and create_search into ONE brief. Omit it on the first call: the answer gives one; pass it to every later assistant call and to create_search of the same new search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations mark this as non-read-only and non-idempotent, and the description corroborates that by disclosing the brief/quota cost and the one-call-per-assistant limit, which is real behavior an agent cannot see in the schema. It also explains that an onboarding_id is minted on the first call and must be threaded through later calls. It stops short of describing the shape of the returned goals or what happens on a repeat call.

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?

The step number and purpose are front-loaded, and every sentence carries operational information (input source, user choice, brief cost, id propagation). It is dense with parentheses and appends a REST endpoint that adds little for an agent, which keeps it from a 5.

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?

There is no output schema, yet the description conveys what comes back (four goals for the user to pick from or write their own, plus an onboarding_id on the first call). Combined with the quota warning and id-threading instructions, an agent has enough to call it correctly in sequence; only the exact response format is unspecified.

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 coverage is 100%, so both parameters are already fully documented, including the pattern and the omit-on-first-call rule for onboarding_id. The description reinforces that company is the step-1 description and that onboarding_id ties calls into one brief, but adds no format or edge-case detail beyond the schema. Baseline 3 is appropriate.

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 gives a specific verb and resource: it produces four outreach goals derived from the company description, with an example ("invite to a call"). The onboarding step framing ("Step 2 «Цель»") plus the explicit input source distinguishes it well from siblings such as suggest_company_description or suggest_outreach_essence, though it never names an alternative outright.

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?

It states the context of use (the onboarding of a new search, after step 1) and a concrete constraint: the first assistant call of an onboarding spends one brief, and a free account may call each assistant once. It also tells the caller to pass the returned onboarding_id onward and to create_search. What is missing is any explicit when-not-to-use condition or named alternative tool.

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