Skip to main content
Glama

Describe the company (onboarding step 1)

suggest_company_description

Step 1 of a new search («Компания»): reads the user's company site (url) or a text about it and writes a short plain-language description of what it sells, to whom and why it matters. The user may edit it before create_search. Takes up to a minute. 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/company]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "suggest_company_description"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoThe company's site, e.g. acme.com.
textNoOr: a text about the company.
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

A4.1/5.0
Behavior4/5

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

Annotations only declare the generic safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false); the description adds genuinely useful behavior: latency of up to a minute, the one-brief/once-per-assistant quota constraint on a free account, and that the user can edit the result before it is committed to a search. It does not spell out what happens on a repeated call or what the response object contains beyond onboarding_id.

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?

Front-loads the purpose and keeps the flow/quota notes brief; every clause carries information. The parenthetical quota sentence is dense and would read better split out, and the Russian label plus REST note add mild clutter, but waste is minimal.

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 correctly supplies the essential return fact (an onboarding_id) plus latency and the onboarding sequencing, which is enough for correct invocation. Missing only edge behavior, such as what occurs if both url and text are supplied or if the call is repeated within a brief.

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 the meaning of url, text and onboarding_id is already documented in the schema. The description confirms the url-vs-text choice and the onboarding_id threading, but largely restates rather than extending the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource: reads the company site (url) or a text and writes a short plain-language description of what it sells, to whom and why it matters. It also anchors itself as "Step 1" of a new search, which distinguishes it from the suggest_* siblings that belong to later onboarding steps.

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?

Gives clear context: this is the first assistant call of an onboarding, its output is user-editable before create_search, and the returned onboarding_id must be forwarded to later assistant calls and create_search. It stops short of explicitly stating when NOT to use it (e.g. mid-onboarding or on an existing search), so it is strong but not fully routable guidance.

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