Mentornity

My meetings

list_meetings

Read-onlyIdempotent

The person's meetings: upcoming (soonest first) or past (newest first) in one programme, or, with from, every meeting on the given days ("who am I meeting today?") in one programme or, without program, in all of them. Each meeting lists the people or group it is with, by member id and role, for reading their profiles.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_meetings"
  }
}

Input Schema

Name	Required	Description
`days`	No	With `from`: how many days (default 1).
`from`	No	First day, YYYY-MM-DD: list the meetings on these days (today, tomorrow, a week).
`when`	No	Default upcoming. Ignored with `from`.
`program`	No	Programme id or domain. Required unless `from` is given (then empty = all programmes).
`with_member_id`	No	Only meetings with this person (optional).

Output Schema

Name	Required	Description
`from`	No	First day, YYYY-MM-DD.
`note`	No	Extra information.
`count`	No	Number of meetings listed.
`until`	No	Last day, YYYY-MM-DD.
`meetings`	No	meeting_id, start, end, with, place, status.
`time_zone`	No	The programme's time zone.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds value by disclosing ordering behavior (soonest first vs newest first) and that each meeting carries the people/group by member id and role. It does not mention limits or pagination, which is the main remaining gap.

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

Conciseness3/5

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

It is front-loaded with the resource and free of filler, but the single run-on sentence with nested 'or...or...' clauses is dense and takes effort to parse. Splitting the three modes into separate sentences would improve readability without losing content.

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 5-parameter read tool with an output schema and full annotation coverage, the description covers all modes and parameter interactions adequately, and the output schema relieves it of explaining return shape. The only omission is pagination/limits, which is minor here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds genuine cross-parameter meaning beyond the schema: `from` switches to day-based listing, `when` is ignored with `from`, and an empty `program` means all programmes. These interaction rules are not fully derivable from the individual field descriptions alone.

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 verb and resource (list the person's meetings) and clearly delineates the three modes: upcoming (soonest first), past (newest first), and date-range via `from`. It is unmistakably distinct from a single-meeting getter, though it does not explicitly name the sibling get_meeting as the alternative for a single record.

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 concrete usage scenarios, including the 'who am I meeting today?' framing for `from`, and explains mode interactions such as 'without `program`, in all of them.' It stops short of stating when NOT to use it or routing to a specific alternative, so it is strong context but not exhaustive guidance.

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

All Mentornity tools Inspect

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

Need Help?