Skip to main content
Glama

Join a Coral couples quiz

coral_quiz_join

Joins an existing quiz using the 8-character invite code from the partner. Returns a participant token and the ten questions. A quiz holds at most two people.

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": {
      "inviteCode": "<inviteCode>"
    },
    "name": "coral_quiz_join"
  }
}

Input Schema

NameRequiredDescriptionDefault
inviteCodeYesThe 8-character invite code from the partner.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-idempotent, closed-world mutation, and the description adds real context on top: joining mints a participant token, returns the ten questions, and is capped at two people per quiz — a concrete failure condition the agent would otherwise not anticipate. It stops short of saying what happens on an invalid or expired code.

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

Conciseness5/5

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

Three short sentences, front-loaded with the action and the required input, then the return payload, then the capacity constraint. Every sentence carries information an agent needs; nothing is padded.

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 single-parameter join tool with no output schema, the description covers what is required to call it and even summarizes the return (token plus ten questions). The only omission is error behavior for an invalid code or an already-full quiz.

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 coverage is 100% and the schema already documents inviteCode as the 8-character partner code. The description restates the same fact without adding format nuances, so it neither compensates for a gap nor adds meaning beyond the structured field.

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 ("Joins an existing quiz") plus the mechanism (8-character invite code from the partner), which implicitly separates it from coral_quiz_start. It does not explicitly name the sibling it contrasts with, so the differentiation is inferable rather than stated.

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?

"using the 8-character invite code from the partner" implies the prerequisite: you need a code a partner gave you, and a quiz must already exist. There is no explicit when-not guidance (e.g., what to do if you already joined, or if the quiz is full) and no named alternative such as coral_quiz_status.

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