Skip to main content
Glama

exam_start

Start an exam run: returns the question and termsHash; the clock starts and an unsubmitted run counts as a fail. Sign typed_data(ExamStart). Submit with POST /exam-runs/{runId}/submit (x402 fee).

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": {
      "exam": "<exam>",
      "agent": "<agent>",
      "nonce": "<nonce>",
      "deadline": "<deadline>",
      "signature": "<signature>"
    },
    "name": "exam_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
examYes
agentYes
nonceYes
deadlineYes
signatureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With zero annotations the description carries the full burden and does well: it discloses the failure consequence (unsubmitted run = fail), that a clock starts, the required signature over typed_data(ExamStart), and the separate fee-bearing submit step. It omits idempotency, retry behavior, and what happens on signature mismatch, keeping it below 5.

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 dense clauses: what it does and returns, the signing prerequisite and failure rule, then the submit path. Nothing is wasted and the core action is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description compensates for the missing output schema by naming the two returned values, and it covers the lifecycle rules around the call. But for a 5-required-parameter mutation-signing tool with no annotations, leaving nonce/deadline/agent semantics unaddressed is a real gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and all five parameters (exam, agent, nonce, deadline, signature) are undocumented in both schema and description. The mention of signing typed_data(ExamStart) indirectly covers signature and hints the typed-data fields matter, but nonce and deadline — likely anti-replay and expiry, both consequential — are left entirely unexplained.

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+resource ('Start an exam run') and what comes back ('returns the question and termsHash'), which is enough to distinguish it from list-style siblings like exams. It stops short of explicitly saying how it relates to the sibling exams tool, but the purpose is unambiguous.

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?

Gives real invocation context: you must first sign typed_data(ExamStart), and submission happens elsewhere via POST /exam-runs/{runId}/submit with an x402 fee. It also warns that an unsubmitted run counts as a fail, which materially shapes when an agent should call it. No explicit exclusions or named alternatives, so not a 5.

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