Skip to main content
Glama
Sign In

Meetful

by com.meetful
OverviewDiscussionsAdmin

Find open times

find_times
Read-only

Lists open times on someone's Meetful booking link (meetful.com/), as exact UTC instants and in the owner's time zone, with the meeting lengths and any questions the page asks. No sign-in needed.

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. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, openWorldHint=false), and the description adds genuinely new context: no sign-in is required, times are returned both as UTC instants and in the owner's time zone, and the payload includes meeting lengths and page questions. It stops short of saying what happens for an invalid or private link.

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?

A single front-loaded sentence with no filler, and the link-scoping constraint plus the no-sign-in note are placed early. It is dense enough that the return-value clauses run together, but nothing is wasted.

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 only four fully-described parameters, no output schema, and annotations covering the safety profile, the description is nearly sufficient, including return-value content. Minor gaps remain around failure behavior for bad links and the effective bounds of the lookup.

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 days, from, link, and minutes are already documented, and the description adds little beyond confirming that 'minutes' maps to the meeting lengths offered. Baseline 3 applies since the schema does the explanatory work.

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 ('lists open times on someone's Meetful booking link') and pins down the response shape (exact UTC instants, owner's time zone, lengths, page questions). It is clearly an availability-read, distinguishable from a booking action such as book_time.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer this is the lookup step before booking, but the definition never says when to prefer it, nor does it name the booking counterpart or note any conditions under which it should not be called.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Meetful 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