Find the next session for a league you belong to.
| Name | Required | Description | Default |
|---|---|---|---|
| league | Yes | Exact MYOPL league slug from its link, for a league the signed-in account belongs to. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Input schema / descriptionAdded value: +"Arguments for get_my_next_session."Input schema / properties / league / descriptionAdded value: +"Exact MYOPL league slug from its link, for a league the signed-in account belongs to."Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "description": "MYOPL structured response for get_my_next_session.",
+ "oneOf": [
+ {
+ "additionalProperties": false,
+ "properties": {
+ "date": {
+ "description": "Next session date as displayed by MYOPL.",
+ "type": "string"
+ },
+ "league": {
+ "description": "MYOPL league slug.",
+ "type": "string"
+ },
+ "league_name": {
+ "description": "League display name.",
+ "type": "string"
+ },
+ "time": {
+ "description": "Next session time as displayed by MYOPL.",
+ "type": "string"
+ }
+ },
+ "required": [
+ "league",
+ "league_name",
+ "date",
+ "time"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "error": {
+ "description": "Tool execution or argument error; the enclosing result has isError set to true.",
+ "type": "string"
+ }
+ },
+ "required": [
+ "error"
+ ],
+ "type": "object"
+ }
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds the meaningful access constraint that the league must be one the signed-in account belongs to, which is genuine context beyond the annotations, but says nothing about latency, missing sessions, or behavior when none exists.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler, no restated name, and no redundancy. Every word contributes to scope.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With one fully documented parameter, an output schema covering return values, and annotations covering safety, the description is appropriately lean. The only gap is that 'next session' is not defined in terms of ordering or time zone, a minor ambiguity for a query tool of this simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single 'league' parameter is already documented in detail (exact MYOPL slug, membership requirement, pattern). The description's only added nuance is the ownership constraint, which largely duplicates the schema text, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Find') and resource ('next session') scoped to 'a league you belong to', which clearly separates it from siblings like get_my_rating or get_my_statistics_card. It does not explicitly name or contrast those siblings, so it stops short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no when-to-use, when-not-to-use, or alternative routing. The only hint is the implicit membership condition ('a league you belong to'), with no guidance on what to do for leagues you don't belong to or how this relates to get_my_action_status or prepare_my_rsvp.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.