ypt-mcp

by derived-functor

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_my_groups

Retrieve the study groups you have joined, including each group's ID, title, category, owner, slogan, and member count.

Instructions

Return the list of study groups you have joined.

:returns: List of group mappings with ``id``, ``title``, ``category``,
    ``owner``, ``slogan`` and ``member_count``.
:rtype: list[dict[str, Any]]
:raises RuntimeError: If YPT credentials are not configured.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

A3.5/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the credential precondition ('raises RuntimeError if YPT credentials are not configured') and enumerates the returned fields. It does not state rate limits, pagination, or cache behavior, but the auth requirement is the meaningful non-obvious trait.

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?

The core sentence is front-loaded and short, but it is followed by reStructuredText boilerplate (:rtype:, :returns:) that duplicates the output schema rather than adding agent-relevant information. Roughly half the text is structured noise.

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?

An output schema exists, so the field enumeration is redundant, and the credential-failure behavior covers the main non-obvious risk. For a zero-parameter read tool this is nearly complete; only pagination or scope caveats are missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool is 4. The description correctly presents this as a no-argument listing call.

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?

States a specific verb and resource ('Return the list of study groups') and scopes it with 'you have joined', which implicitly separates it from browse_groups (all groups) and get_group_members. It stops short of naming any sibling explicitly, so the differentiation must be inferred.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites section, and no mention of alternatives such as browse_groups for discovering groups you have not joined. The only hint at context is the phrase 'you have joined', which merely restates the tool's identity rather than giving selection criteria.

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

Deploy Server