Skip to main content
Glama

My matches

list_my_matches
Read-onlyIdempotent

The person's mentor/mentee pairs in a programme: active matches and requests sent or received, with the match id other tools take.

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": {
      "program": "<program>"
    },
    "name": "list_my_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
programYesId or domain of one of the person's programmes.

Output Schema

NameRequiredDescriptionDefault
matchesNomatch_id, with (member_id, name), you_are, status, since.
programNoProgramme domain.
statusesNoWhat each status means.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world and non-destructive behavior, so the description's added value is in disclosing that both confirmed matches and pending requests are returned together, which affects how results should be interpreted. It also signals the match id is the key consumed by downstream tools, useful workflow context beyond the annotations.

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?

One front-loaded sentence with no filler; the contents (active matches, requests) and the practical outcome (match id) come in the right order. The phrasing 'The person's mentor/mentee pairs' is slightly awkward but still compact.

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 a rich schema, full annotations and an output schema, the description only needs to frame scope and the result's purpose, which it does. The one remaining gap is that it never points to list_my_programs as the way to obtain a valid programme identifier.

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% and the single 'program' parameter is fully documented in the schema as an id or domain of one of the person's programmes. The description only echoes 'in a programme' without adding format or lookup guidance such as how to obtain a valid programme id.

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 names the resource (mentor/mentee pairs, i.e. matches), the scope ('in a programme', 'the person's'), and what the listing contains (active matches plus sent/received requests). That is a specific verb-less but clear listing purpose, and 'the person's' distinguishes it from generic searches like search_mentees or search_mentors.

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 only implied: 'the match id other tools take' hints this is the lookup step before acting on a match, and 'in a programme' implies a programme must already be known. There is no explicit when-to-use or when-not, and no named alternative such as search_mentees for finding people who are not yet matched.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources