Fun Friday

Fun Friday team and plan

funfriday_get_team

Read-only

Get the user's Fun Friday team: its name, how many members it has, which plan it is on, how many of this week's games remain, and how many custom packs it has and may keep. Use this before hosting to check the team has a game left, before funfriday_create_pack to check there is room for a pack, or to answer questions about the plan and its limits.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`plan`	Yes
`team`	Yes
`max_players`	Yes
`week_resets_at`	No
`custom_packs_used`	No
`custom_packs_limit`	No	How many custom packs the team may keep: 0 when its plan has none, null when unlimited.
`max_games_per_week`	No
`playable_game_types`	No
`games_used_this_week`	No
`games_remaining_this_week`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 6, 2026

addedOutput schema / properties / custom_packs_limit

Added value: +{
+  "description": "How many custom packs the team may keep: 0 when its plan has none, null when unlimited.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / custom_packs_used
```
Added value: +{
+  "type": "number"
+}
```

First observedOct 4, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. Most of what the description adds is a restatement of return fields, and the tool has an output schema that already documents those, so genuine behavioral value beyond structured data is limited to the implicit 'this week's games' / pack-retention framing.

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?

A single, front-loaded sentence that opens with the purpose and then layers on usage conditions. It is slightly dense — the field enumeration arguably belongs to the output schema — but no sentence is wasted or redundant within itself.

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 zero-parameter read tool with annotations covering safety and an output schema covering return shape, the description supplies everything an agent needs to decide to call it. The only shortfall is that it spends budget re-describing outputs rather than adding scope or freshness caveats.

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 and additionalProperties is false, so there is nothing for the description to disambiguate. Baseline of 4 applies; no parameter guidance is needed or missing.

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?

It states a specific verb and resource ('Get the user's Fun Friday team') and then enumerates exactly what that returns — name, member count, plan, games remaining this week, custom packs and keep limit. That enumeration is enough to tell it apart from siblings like funfriday_get_session or funfriday_get_leaderboard without opening either schema.

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

Usage Guidelines5/5

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

Three concrete trigger conditions are given: before hosting (to confirm a game remains), before funfriday_create_pack (to confirm pack capacity), and to answer plan/limit questions. An alternative tool is named with the condition that selects it, leaving nothing to inference.

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

All Fun Friday 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?