Skip to main content
Glama
Sign In

TeamMeet

by io.github.theguysaccount
OverviewDiscussionsAdmin

Find open times

find_times
Read-only

Open times on someone's Meetful booking link (meetful.com/ or meetful.com/book/), to book one for your person with book_time. No key needed. Times come back as exact UTC instants and in the owner's own time zone, with the page's lengths and any questions it asks.

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": {
      "link": "<link>"
    },
    "name": "find_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days to look across, 1 to 30. Default 7.
fromNoThe first day to look at, YYYY-MM-DD in the owner's calendar. Default: today.
linkYesThe booking link, or just the name in it: "meetful.com/jack" or "jack".
minutesNoHow long, when the page offers more than one length.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds real value on top: the exact shape of the returned data (UTC instants plus the owner's local time zone, the page's offered lengths, and the questions the page asks). It says nothing about failure behavior for invalid or private links, which is the remaining gap for a read tool with no output schema.

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?

Two sentences, front-loaded with the resource and scope, then the follow-up action and return shape. Dense but every clause carries information; the URL examples are slightly redundant with the schema but serve as a quick syntax reminder.

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?

With no output schema, the description takes on the burden of explaining what comes back and does so (UTC instants, owner time zone, page lengths, questions). Four parameters are fully documented elsewhere via the schema. Only error/permission edge cases are unaddressed, so it is nearly complete for a read-only lookup tool.

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 description coverage is 100%, including ranges and defaults for days and the accepted short form for link, so the schema already carries the semantics. The description adds only a little beyond that: the alternate /book/<name> URL form and the idea that minutes corresponds to a length the page offers. That is marginal added meaning against an already-complete schema.

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+resource (find open times on a Meetful booking link), names the exact URL forms it accepts, and explicitly distinguishes itself from the sibling book_time, which is the action that consumes the result. An agent can tell immediately this is the discovery step before booking.

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?

The description gives a clear use chain: call this to see open times, then call book_time to reserve one. It also removes an auth prerequisite with 'No key needed.' It does not cover exclusions, such as what to do when a link is private or a person has no page, 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.

All TeamMeet toolsInspect
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