Skip to main content
Glama

Read a Flypost workflow guide

flypost_guide
Read-only

Which Flypost tool to use for which job, for one area, with the steps in order. Read it before you start work in that area. images: making, changing, checking and branding any visual (carousels, infographics, Image posts, a picture for a text post), and putting the user's own image or screenshot on a post, a slide or inside a design.

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": {
      "topic": "<topic>"
    },
    "name": "flypost_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 openWorldHint=false, so the safety profile is covered. The description adds that the response is ordered steps mapping jobs to tools, which is genuine value beyond the annotations. It does not say how large the guide is, whether it covers every tool in the area, or what happens for an area not yet supported.

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?

The routing purpose and the 'read before starting' instruction are front-loaded, and the topic enumeration is dense but each clause maps to a real sub-area. The opening is a verbless fragment and the topic sentence runs long, which costs some readability but not correctness.

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?

This is a low-complexity, read-only lookup tool with one enum-constrained parameter and no output schema, so the description carries most of the burden. It explains what the guide answers and what the topic value includes, which is enough for an agent to call it correctly; only the guide's breadth and granularity remain unspecified.

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 description coverage is 0% and the single 'topic' parameter is an enum with only one value ('images'), which alone would be opaque. The description compensates by spelling out what that area covers: making, changing, checking and branding visuals, carousels, infographics, image posts, and placing a user's own image on a post, slide or design. That materially expands the meaning of the enum value.

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 states a specific resource (a Flypost workflow guide) and its function: mapping which tool to use for which job, with ordered steps for one area. It also scopes that area ('images') with concrete examples, so an agent can tell this is a meta-routing guide rather than a content-producing tool. It stops short of naming the sibling tools it routes to, which keeps it from a 5.

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?

'Read it before you start work in that area' is an explicit when-to-use instruction tied to a precondition. There is no when-not guidance or explicit statement of alternatives, but the 'before you start' framing makes the sequencing clear enough to act on.

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.