FeedSquad

Find Next Available Slot

find_next_slot

Read-onlyIdempotent

Returns the next available posting slots for one platform (count: default 3, max 10), honoring Handler's daily caps (5 X / 3 Threads / 2 LinkedIn per day), its spacing rules (90min / 2h / 4h) and the posts already scheduled, with a rationale and each slot in UTC and in the founder's timezone. Takes a platform and a count only; it accepts no date or time window. It does not apply the founder's posting window or campaign mode, so the slot Handler assigns when a single post is created without a time can differ from these. Planning only: it writes nothing. platform=bluesky or mastodon returns an error, because publishing to them isn't available yet.

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": {
      "platform": "<platform>"
    },
    "name": "find_next_slot"
  }
}

Input Schema

Name	Required	Description	Default
`count`	No	Number of slots to return (default 3, max 10).
`platform`	Yes	The platform to find slots for. bluesky and mastodon are accepted for compatibility but return an error: publishing to them isn't available yet.

Output Schema

Name	Required	Description	Default
`kind`	Yes
`slots`	Yes
`monthly`	Yes
`spacing`	Yes
`capacity`	Yes
`platform`	Yes
`timezone`	No
`rationale`	Yes
`considered`	No
`server_now`	No
`slots_local`	No
`not_available`	No
`timezone_source`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing daily caps (5 X / 3 Threads / 2 LinkedIn), spacing rules (90min / 2h / 4h), that scheduled posts are respected, the UTC plus founder-timezone output, and the error behaviour for unsupported platforms. The one gap is that it never says what the 'rationale' string contains or how empty/full calendars change the result shape. Given annotations already cover the safety profile, this is strong but not exhaustive.

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?

Dense but front-loaded: capability, then limits, then caveats, then error case. It is one long paragraph of run-on clauses, so a reader must work to parse it, but no sentence is filler.

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?

Covers inputs, constraints, and non-applied modifiers thoroughly, and an output schema exists so return values needn't be spelled out. Minor omission is what happens when no slots are available within limits.

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 coverage is 100%, so default/max on count and the enum restrictions are already documented; the description's added value is only the reminder that no other parameters (no date or time window) are accepted. Baseline 3 plus that negative-space clarification earns a 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Returns the next available posting slots') and constrains scope to one platform, distinguishing it from siblings like get_calendar or create_post that also deal with scheduling.

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

Usage Guidelines5/5

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

Explicitly says it takes only a platform and count with no date/time window, that it is planning-only and writes nothing, and that bluesky/mastodon error out. It also warns that Handler's slot on a single untimed post can differ because posting windows and campaign mode aren't applied, giving an agent a clear condition for choosing this versus create_post.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All FeedSquad tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?