Skip to main content
Glama

Build first ideas during setup

flypost_build_first_ideas

Build the project's writing voice and first post ideas from everything gathered in setup. If an earlier attempt failed, this tries again. Check progress with flypost_get_onboarding_status.

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_build_first_ideas"
  }
}

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 a non-read-only, non-destructive, closed-world mutation, so the description's job is to add context beyond that. It usefully implies a long-running operation whose state must be polled, but says nothing about whether it overwrites an existing voice or existing ideas, what inputs from setup it consumes, or what happens on repeated invocation.

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?

Three short sentences, front-loaded with the purpose before the retry note and the progress pointer. "From everything gathered in setup" is slightly vague but no sentence is wasted.

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

Completeness3/5

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

For a one-parameter, no-output-schema setup tool, the description covers purpose, retry, and progress checking, which is the core an agent needs. It still omits prerequisites (whether sources and brand must be added first via the onboarding tools) and any sense of how long the build takes.

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% and the single project_id parameter is fully documented in the schema, including the omit-to-use-active-project fallback. The description adds no parameter meaning at all, which is acceptable at this coverage but earns only the baseline.

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 two concrete outputs: "Build the project's writing voice and first post ideas" from setup material. That distinguishes it from siblings like flypost_brainstorm_ideas or flypost_create_draft, though it never explicitly says so, leaving the differentiation to inference.

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?

"If an earlier attempt failed, this tries again" establishes retry semantics, and "Check progress with flypost_get_onboarding_status" names a concrete companion tool. It lacks an explicit when-not or a comparison against flypost_brainstorm_ideas for ongoing idea generation, so it falls short of full routing 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.