Skip to main content
Glama

Fill from an earlier onboarding

get_onboarding_prefill
Read-onlyIdempotent

The answers of an earlier onboarding (company, goal, icp, language) to reuse in create_search; pass its id as source_task there too, so the search plan made then is reused when the brief stays the same. [REST: GET /api/onboardings/{id}]

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

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.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds the REST endpoint and the cross-tool effect of reusing a prior search plan, but does not say what happens if the onboarding no longer exists or whether answers are partial. With annotations carrying the behavioral burden, this is adequate but not rich.

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?

A single dense sentence with a parenthetical field list and a REST tag; every clause carries information and the reuse purpose comes before the endpoint detail. It reads as an elliptical fragment rather than a well-formed statement, which costs a little clarity.

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

Completeness5/5

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

For a one-parameter read tool with no output schema, the description supplies the returned fields, the consumer (create_search), and the downstream consequence of reuse. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3; the description goes further by explaining that the identifier is reused as source_task in create_search, a relationship not visible in the schema. The value is slightly muddied because the schema calls the field task_id ('the search id') while the endpoint takes /api/onboardings/{id}, leaving some ambiguity about which entity the id refers to.

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 resource (the answers of an earlier onboarding) and enumerates the content returned (company, goal, icp, language), which is specific enough to distinguish it from get_search or get_search_requirements. It is a verbless fragment, so the action ('fetch/retrieve') must be inferred, but the REST path GET /api/onboardings/{id} confirms it is a read of a single prior onboarding.

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?

Usage is stated concretely: reuse these answers in create_search and pass the same id as source_task there, with the qualifying condition 'when the brief stays the same'. There is no explicit when-not guidance (e.g., when to build a fresh brief instead), which keeps it short of a 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