Skip to main content
Glama

Find the next free posting slot

clipember_find_next_free_slot
Read-onlyIdempotent

Find the earliest upcoming posting slot that is free on every given account — each account's preferred posting times (clipember_list_posting_slots), skipping times where the account already has a queued post or draft within 30 minutes. Returns one time for all accounts plus each account's own next free slot. To post then, pass the time as scheduledFor to clipember_create_post.

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": {
      "connectionIds": "<connectionIds>"
    },
    "name": "clipember_find_next_free_slot"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoSearch from this time (ISO 8601); default now
connectionIdsYesAccounts (connectionId from clipember_list_platform_connections)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely non-obvious behavior: preferred posting times per account and a 30-minute conflict window against queued posts and drafts. It also discloses the return shape ('one time for all accounts plus each account's own next free slot'), which matters because there is no output schema. The one uncovered case is what happens when no shared slot exists — no empty-result behavior is stated.

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?

Three front-loaded sentences with no filler: definition and conflict rule first, return shape second, next-step routing last. Every clause carries information an agent needs to call or chain the tool.

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 two-parameter read-only tool with full schema coverage and no output schema, the definition covers mechanics, conflict handling, and return shape. The remaining gap is the no-availability case, which an agent may hit in practice with narrow schedules.

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 100%, so baseline is 3, but the description adds real meaning: connectionIds is framed as the set of accounts whose schedules must intersect, and 'after' is implicitly the search origin for the earliest-slot scan. That intersection semantics is not expressible in the schema alone.

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 ('Find the earliest upcoming posting slot') and immediately pins down the scope ('free on every given account'), which is the distinguishing semantics versus a per-account slot listing. It also names the sibling (clipember_list_posting_slots) that supplies the underlying preferred-times data, so an agent can tell the two apart without opening a schema.

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?

Explicit follow-on routing is given ('To post then, pass the time as scheduledFor to clipember_create_post'), and the cross-account intersection framing implies this is the multi-account variant of clipember_list_posting_slots. It stops short of an explicit 'use X instead when you only need one account's raw slot list' exclusion, but the context is otherwise unambiguous.

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.

Resources