Skip to main content
Glama

Submit answers to a Coral couples quiz

coral_quiz_submit
Idempotent

Saves one person's answers to a quiz they started or joined: one option for each of the ten questions. When both people have submitted, the reply includes the shared comparison, which shows only the answers both people chose. Submitting again changes nothing.

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>",
      "answers": "<answers>"
    },
    "name": "coral_quiz_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
answersYesOne answer per question. Every question must be answered.
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

A4.2/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, and the description restates the idempotency more concretely ("Submitting again changes nothing") while adding a genuine behavioral fact the annotations lack: the reply conditionally contains a shared comparison limited to answers both people chose. That output-behavior disclosure is valuable, though it leaves error cases (wrong or incomplete answers) unaddressed.

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 scope, then the outcome, then the idempotency note. No filler and nothing repeated verbatim except a brief restatement that reinforces the idempotent behavior.

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 no output schema, the description does the work of explaining the conditional return value (the shared comparison) and confirms that resubmission is harmless. For a three-parameter submission tool that is largely sufficient; only the failure modes for incomplete or invalid answers are left unspecified.

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 the baseline is 3. The description adds a little — it links the answers array to "the ten questions" and the one-option-per-question constraint, which clarifies that the array must be fully populated despite the schema's permissive 1–20 range. It says nothing about sessionId or participantToken beyond what the schema already documents.

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?

The description names a specific verb and resource ("Saves one person's answers") and scopes it precisely: one option for each of the ten questions, tied to a quiz the person "started or joined." That phrasing distinguishes it from the sibling start/join/status tools without needing to open any schema.

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

Usage Guidelines4/5

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

Usage context is clear from the phrase "started or joined" and from the mention that a result appears "when both people have submitted" — the agent can infer this is the step after start/join and the trigger for the comparison. However, it never explicitly names an alternative (e.g., coral_quiz_status) for checking progress before submitting, so there are no stated exclusions.

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