Skip to main content
Glama

find_available_slot

Read-onlyIdempotent

Find available time slots for posting. Respects a 1-hour gap between posts and preferred hours. Without timezone it uses the saved user timezone (in a shared workspace, the timezone of that workspace first), then UTC; the result names the timezone used and where it came from, and says so when it fell back to UTC. Each slot includes the UTC instant to pass as scheduled_at. strategy "best_engagement" (needs account_ids) ranks the next 7 days by when these accounts get the most engagement, with a 1-5 star rating and a reason per slot.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_available_slot"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of slots to return (max 10). Default 5 for next_free, 3 for best_engagement.
strategyNonext_free: earliest free slots. best_engagement: best times by engagement (requires account_ids).next_free
timezoneNoIANA timezone, e.g. Europe/London
account_idsNo
workspace_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, closed-world, so the safety bar is low. The description adds real context beyond that: the timezone fallback chain (user → shared-workspace → UTC), that the response names the timezone and its source, and that a UTC fallback is flagged. It doesn't cover pagination or what happens with zero available slots, but the disclosure is strong.

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?

Purpose is front-loaded in the first clause and every later sentence carries operational detail. The third sentence is dense and run-on, mixing timezone resolution, output shape, and the best_engagement strategy, but nothing is genuinely redundant.

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?

There is no output schema, so the description must describe return values — it does: timezone used and its source, UTC instant per slot, and star rating plus reason for best_engagement. Combined with the timezone fallback rules, an agent has enough to call this correctly without further probing.

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 60%, and the description fills the most important gap: the meaning and resolution order of `timezone`, plus the account_ids dependency for best_engagement. It also clarifies that the returned UTC instant is what to pass as scheduled_at. workspace_id is never explained in either place, which is the remaining shortfall.

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 available time slots for posting') and immediately scopes what the slots respect (1-hour gap, preferred hours). An agent can distinguish this scheduling-lookup tool from write tools like create_post or analytics tools without opening the 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?

Explains the two strategies and the condition that selects one ('best_engagement' needs account_ids, ranks next 7 days), and gives per-strategy count defaults. It lacks an explicit statement of when not to use it or a named alternative sibling, which keeps it below a 5.

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