Skip to main content
Glama

Check a Coral couples quiz

coral_quiz_status
Read-onlyIdempotent

Checks a quiz without changing it. Says whether the partner has answered, and returns the shared comparison once both have. Needs the session ID and the participant token.

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": {
      "sessionId": "<sessionId>",
      "participantToken": "<participantToken>"
    },
    "name": "coral_quiz_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYesThe session ID returned when the quiz was started or joined.
participantTokenYesThis person's participant token, returned when they started or joined the quiz.

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 already declare readOnly, idempotent, non-destructive and non-open-world, so the safety profile is covered structurally. The description adds genuinely new behavioral detail not in the annotations: the response is staged, saying only whether the partner has answered until both have, then returning the shared comparison. It says nothing about invalid/expired token behavior, which is the main remaining gap.

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?

Two short sentences, no filler, and the key constraint (read-only check) is front-loaded before the response behavior. Every clause carries information the agent needs.

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 only two parameters, rich annotations, and no output schema, the description supplies enough: the read-only nature, the two required inputs, and the two-phase return semantics. Minor omissions are error handling and whether repeated polling is expected, but nothing essential for a correct invocation is missing.

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%, so both parameters are fully documented in the schema, and the baseline is 3. The sentence "Needs the session ID and the participant token" merely restates the required fields without adding format, provenance, or failure-mode meaning beyond the schema.

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?

"Checks a quiz without changing it" gives a specific verb and resource, and the second sentence states exactly what is reported (partner answered status, shared comparison). It implicitly separates this from the mutating siblings (start/join/submit) via "without changing it", but never names an alternative outright.

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?

The phrase "without changing it" implies a read/poll use case, which is useful implied guidance. However, there is no explicit when-to-use framing, no mention of polling cadence, and no stated condition distinguishing this from coral_quiz_submit or the other quiz siblings.

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