Skip to main content
Glama

TestChimp

by io.testchimp
OverviewDiscussionsAdmin

List Meetings

list-meetings
Read-onlyIdempotent

List / search cloud-synced Meeting Bots meetings, newest first, like the Meetings page filters + search. Team-wide meetings only (visibility: all team members). Filters: from / to (YYYY-MM-DD, ISO datetime, or epoch millis; inclusive), labels, participantKeys (user id or email), participantDomains, searchText (full-text over title + transcript; hits include a searchSnippet with matches wrapped in ⟦ ⟧). Returns meetingId, title, startMillis, labels, participants, summaryStatus; page with nextPageToken. Set includeFilterOptions=true for exact label / domain / participant catalogs. Pass meetingSetId for a Start Chat meeting-set (expires after 7 days). Then get-meeting-transcript (summaryOnly first) per hit.

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
botIdNoQA bots: your botId from your stored TestChimp binding.
labelsNo
pageSizeNo
pageTokenNo
searchTextNo
meetingSetIdNo
endDateMillisNo
projectApiKeyNoQA bots: your own project API key from your stored TestChimp binding. Required on every call except get-bot-credentials, get-project-credentials and get-bot-compat. Never print it.
participantKeysNo
startDateMillisNo
participantDomainsNo
includeFilterOptionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / includeFilterOptions
      Added value: +{
+  "type": "boolean"
+}
    • addedInput schema / properties / meetingSetId
      Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / botId
      Added value: +{
+  "description": "QA bots: your botId from your stored TestChimp binding.",
+  "maxLength": 64,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / projectApiKey
      Added value: +{
+  "description": "QA bots: your own project API key from your stored TestChimp binding. Required on every call except get-bot-credentials, get-project-credentials and get-bot-compat. Never print it.",
+  "maxLength": 256,
+  "minLength": 8,
+  "type": "string"
+}
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds real value beyond them: team-wide visibility limitation, newest-first ordering, search hits returning a searchSnippet with ⟦ ⟧ match markers, and a 7-day expiry on meetingSetId. Minor gap: no note on rate limits or result caps per page.

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?

Front-loaded with the core action and scope, then filters, then return shape, then next step — a sensible ordering. It is dense and parenthetical-heavy but nearly every clause carries information; a little more sentence structure would help.

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?

Given 14 parameters and no output schema, the description does well to state the returned fields (meetingId, title, startMillis, labels, participants, summaryStatus) and pagination via nextPageToken. The undocumented startDateMillis/endDateMillis pair and the unmentioned projectApiKey/botId auth params leave a small but real gap.

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 only 14%, so the description must compensate and it partially does — it explains from/to formats (YYYY-MM-DD, ISO, epoch millis, inclusive), participantKeys accepting user id or email, and searchText semantics. However it omits startDateMillis/endDateMillis entirely (a second date pair alongside from/to, creating ambiguity), plus pageSize, botId, and projectApiKey requirements.

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 ('List / search cloud-synced Meeting Bots meetings'), plus scope (team-wide only, newest first) and a behavioral anchor ('like the Meetings page filters + search'). An agent can distinguish it from get-meeting-transcript and other list-* siblings immediately.

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?

Explicitly routes the agent onward ('Then get-meeting-transcript (summaryOnly first) per hit') and explains when to use includeFilterOptions and meetingSetId. Lacks an explicit 'when not to use this' exclusion, keeping it at 4 rather than 5.

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

All TestChimp toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources