Skip to main content
Glama

Prepare to schedule a post

flypost_prepare_schedule
Read-only

Read a draft together with the LinkedIn identities it can be posted as and the posts already scheduled, for choosing a day and time to schedule it. Read-only: it schedules nothing.

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": {
      "draft_id": "<draft_id>"
    },
    "name": "flypost_prepare_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoThe day the user asked to post on, as YYYY-MM-DD in the user's own time zone. The card opens on this day.
timeNoThe time the user asked for, as 24-hour HH:MM in the user's own time zone. The card opens on this time; without it the card uses 09:00.
draft_idYes
project_idNoProject id; omit for the active project.

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 declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered; the description nonetheless adds useful behavioral content by enumerating what is read back (draft, postable identities, existing scheduled posts). Since there is no output schema, that enumeration is the only signal about return content. No mention of permission requirements or how far ahead scheduled posts are listed.

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 short sentences, front-loaded with the read scope and closed with the key constraint. No filler, no restatement of the title, and every clause carries information an agent needs.

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?

For a read-only preparation tool with no output schema, the description tells the agent what comes back and that nothing is mutated, which is the essential context. The only real gap is the undocumented draft_id and the absence of an explicit next-step tool, both minor for a four-parameter read.

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 75% with date, time and project_id well documented, including time-zone and default behavior. The description adds no parameter-level detail beyond the schema and leaves draft_id, the only required parameter, unexplained in both places. Baseline 3 is appropriate given the schema does most of the work.

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?

States a specific verb (read) and concrete resources (the draft, its LinkedIn identities, already-scheduled posts) plus the intent behind the read: choosing a day and time. The closing clause 'it schedules nothing' draws a clear line against flypost_schedule_post without naming it, so an agent can distinguish this from the scheduling sibling.

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?

The phrase 'for choosing a day and time to schedule it' establishes the situation in which to call this tool, and 'Read-only: it schedules nothing' acts as a when-not signal. What's missing is an explicit handoff, e.g. that flypost_schedule_post should be called afterwards to actually commit the time.

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.