Skip to main content
Glama

Swift Agent Network: Local Agents, Movers & Contractors

Open times to book a member

open_times
Read-only

The times a network member has free to meet in the next 1 to 7 days, the same times their booking page shows, each with their UTC offset, plus the meeting length, where it happens and book_url. This server does not book: give the person book_url so they pick a time and book it themselves. A member who does not take bookings here gets taking_bookings false and the public ways to reach them.

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": {
      "slug": "<slug>"
    },
    "name": "open_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days ahead to look, from now.
slugYesThe member's slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover safety (readOnlyHint true, destructiveHint false, openWorldHint false), and the description adds substantial context beyond them. It promises parity with the member's public booking page, discloses the UTC offset, meeting length, location, and book_url, and describes the non-bookable-member branch (taking_bookings false plus public contact routes). Nothing here contradicts the annotations.

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?

The definition front-loads the core payload description, then the no-booking boundary, then the fallback case, so the ordering matches the agent's decision flow. The first sentence is long and stacks several return fields, but every clause earns its place and nothing is 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 carry the return-value burden, and it does: it enumerates the offset, meeting length, location, and book_url, and covers the non-bookable-member outcome. For a two-parameter read tool, the definition supplies everything needed to call it and use the result.

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 100%, so both slug and days are already fully documented in the schema. The description only lightly reinforces the days range by saying 'in the next 1 to 7 days' and does not add format or edge-case meaning. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

The description states a specific resource and scope: a member's free meeting times for the next 1-7 days, including UTC offset, meeting length, location, and book_url. It is clearly distinguishable from get_member, how_to_contact, and search_members because it is explicitly availability, not contact or profile data. It falls short of a 5 only because the leading phrase is a noun phrase rather than an explicit verb ('get'), though 'the same times their booking page shows' makes the intent unambiguous.

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?

It gives clear context (produce a member's bookable times) and an explicit boundary: 'This server does not book: give the person book_url so they pick a time and book it themselves.' It also tells the agent to fall back on the taking_bookings false response and the public contact routes. It does not explicitly name sibling tools as alternatives, so it stops short of 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.