Skip to main content
Glama

Start setup from a website

flypost_start_onboarding

Start setting up a new project from the user's website: Flypost reads it for their brand, business and content sources. Use when the user agrees to set up. Check progress with flypost_get_onboarding_status.

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": {
      "website_url": "<website_url>"
    },
    "name": "flypost_start_onboarding"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idNoProject (workspace) id. Omit to use the active project, or the only project if there is just one.
website_urlYesThe user's company or personal website.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag the mutation and open-world nature, so the bar is lower; the description still adds value by revealing that this kicks off a longer-running process whose progress must be polled separately. It does not cover permissions, idempotency, or what happens if the project already exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences: the action and its effect come first, then the when-to-use condition and the polling pointer. Nothing is padded or repeated.

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, and the description compensates by telling the agent where to look for results. For a two-parameter kickoff tool with annotation coverage, that is close to complete, with only edge-case behavior left unstated.

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 both parameters are already documented, including the project_id fallback behavior. The description only reinforces that website_url is the user's own site, adding little beyond the schema; 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 gives a specific verb and resource ('Start setting up a new project from the user's website') and explains what the tool actually does with that input (reads the site for brand, business and content sources). It is clearly distinct from the status-checking sibling, though it does not distinguish itself from the other onboarding sub-tools.

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 an explicit trigger condition ('Use when the user agrees to set up') and a follow-up route ('Check progress with flypost_get_onboarding_status'). It lacks an explicit 'do not use if onboarding is already in progress' exclusion, 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.