Skip to main content
Glama

get_queue_slots

Read-only

Get the next open queue time for each platform named: the time queue_post would give a post now. Times are ISO 8601 in the workspace's posting time zone. Already booked and penciled times are skipped. A platform with no channel says no_connected_account. A platform with more than one channel lists them; pass platform_account_ids to pick one. "no slot configured" means that channel has no posting times yet (add them with add_queue_times). For the whole weekly schedule, use list_queue_schedule; for posts already booked, use list_scheduled_posts.

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": {
      "platforms": "<platforms>"
    },
    "name": "get_queue_slots"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformsYesPlatforms to check
workspaceNoOptional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.
platform_account_idsNoOptional map of platform => connected_account_id (numeric id from `list_connected_accounts`), for a platform with more than one channel. Example: {"linkedin": 42}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / platform_account_ids
      Added value: +{
      +  "additionalProperties": {
      +    "type": [
      +      "string",
      +      "number"
      +    ]
      +  },
      +  "description": "Optional map of platform => connected_account_id (numeric id from `list_connected_accounts`), for a platform with more than one channel. Example: {\"linkedin\": 42}.",
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so safety is covered; the description adds substantial context beyond that: booked and penciled times are skipped, timestamps are ISO 8601 in the workspace's posting time zone, and per-platform failure states are enumerated (no_connected_account, 'no slot configured'). It does not discuss ordering of returned platforms, pagination (likely N/A), or what a fully-empty result looks like, which is the only remaining gap.

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?

Front-loaded with the core definition and the queue_post equivalence, then error semantics, then sibling routing. Every sentence carries information, but the middle section packs four distinct edge cases into a dense run-on, which slightly reduces scannability for a small tool.

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

Completeness5/5

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

No output schema exists, and the description compensates by specifying the return type (ISO 8601 times per platform, in the workspace time zone) and the two string sentinel results. Combined with the multi-channel and empty-queue edge cases, an agent has everything needed to call and interpret this tool correctly.

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 the baseline is 3; the description earns an extra point by explaining the decision rule for platform_account_ids ('a platform with more than one channel lists them; pass platform_account_ids to pick one'), which the schema does not convey. The workspace parameter's non-persistent semantics are covered by the schema itself, so nothing more is expected here.

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?

Specific verb and resource ('Get the next open queue time for each platform named') plus an operational definition that removes ambiguity: it returns 'the time queue_post would give a post now.' The description explicitly delineates it from queue_post (which acts) and from list_queue_schedule/list_scheduled_posts, so an agent can distinguish it from all relevant siblings 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 Guidelines5/5

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

It names the alternatives and the condition selecting each: whole weekly schedule -> list_queue_schedule, already booked posts -> list_scheduled_posts, and no posting times configured -> add_queue_times. It also states when to pass platform_account_ids (platform with more than one channel), which is genuine routing guidance rather than restated schema.

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