Skip to main content
Glama

Get setup progress

flypost_get_onboarding_status
Read-only

See how far a project is through Flypost's setup and what to do next. Shows the brand found on their website, detected content sources and first ideas when they are ready to review.

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

Input Schema

NameRequiredDescriptionDefault
project_idNoProject (workspace) id. Omit to use the active project, or the only project if there is just one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and a closed world, so safety is covered. The description's real contribution is disclosing conditional content ("when they are ready to review"), which tells the agent some fields may be absent — useful, but it stops short of describing freshness or how progress is computed.

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 sentences, front-loaded with the core action and immediately followed by the payload contents. No filler, no restatement of the title.

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?

A read-only status tool with a single optional parameter is easy to call, and the description covers the return payload even though no output schema exists. Missing only how to interpret or act on the status beyond the vague "what to do next".

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?

Only one parameter (project_id) and its schema description is complete, including the omit-to-default behavior. The description adds no meaning about project scoping, so the schema does all the work — baseline 3.

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?

Names a specific verb and resource: reading a project's progress through Flypost's setup, plus a secondary disclosure of what the response contains (brand, content sources, first ideas). That distinguishes it from the onboarding mutators (start/finish/confirm/add) in the sibling set, though it never names them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"what to do next" implies this is the check-the-state call that precedes acting on onboarding steps, but usage is only implied. There is no explicit when-to-use/when-not framing and no pointer to the sibling tools that advance the flow.

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.