Skip to main content
Glama
Sign In
b2match-mcp

b2match-mcp

by barzoj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Find B2match meeting slots

find_meeting_slots
Read-onlyIdempotent

Find shared free meeting slots for selected participants on one day without booking or requesting a meeting, helping you identify common availability before scheduling.

Instructions

Find free meeting slots shared by the logged-in viewer and selected participants on one day. Read-only: does not book or request a meeting. Use my_availability for your own free time only.

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": {
      "event": "<event>",
      "participant_ids": "<participant_ids>"
    },
    "name": "find_meeting_slots"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNoDay to search, as a days[].date value from my_availability; omit for the default day.
eventYesB2match event URL, slug/euid, or numeric event id.
durationNoB2match MeetingDuration enum value (e.g. THIRTHY, B2match's spelling); omit for the event default.
participant_idsYes1-10 participant ids (from list_participants) to meet with.
is_long_term_networkingNotrue searches the event's long-term networking calendar instead of the main meeting days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.1
    • addedInput schema / properties / day / description
      Added value: +"Day to search, as a days[].date value from my_availability; omit for the default day."
    • addedInput schema / properties / duration / description
      Added value: +"B2match MeetingDuration enum value (e.g. THIRTHY, B2match's spelling); omit for the event default."
    • addedInput schema / properties / is_long_term_networking / description
      Added value: +"true searches the event's long-term networking calendar instead of the main meeting days."
    • addedInput schema / properties / participant_ids / description
      Added value: +"1-10 participant ids (from list_participants) to meet with."
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, so the safety profile is known. The description restates this in domain terms ('does not book or request a meeting'), which is mildly useful emphasis but adds little new information. It says nothing about the 1-10 participant cap, permissions, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with no waste; the core capability is front-loaded and the exclusion follows immediately. Every clause carries routing or scope information.

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?

For a read-only search tool with full schema coverage and annotations, this is nearly sufficient. The only gap is that no output schema exists and the description does not hint at the shape of the returned slots.

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%, so the baseline is 3 — the schema already explains day, event, duration, participant_ids and the long-term flag in detail. The description only reinforces the 'one day' scoping already present in the 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 and resource ('Find free meeting slots') plus the exact scope: shared by the viewer and selected participants, on one day. It explicitly distinguishes itself from my_availability, so an agent can route without opening either 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?

Gives a clear usage context (mutual free time with chosen participants) and names one alternative with its condition ('Use my_availability for your own free time only'). It does not mention meeting_recommendations as a related-but-different option, so the routing picture is clear but not exhaustive.

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

Deploy Server

Other Tools