Skip to main content
Glama
Sign In

DeepMark

by com.getdeepmark.api
OverviewDiscussionsAdmin

Confirm Exam Paper Draft

paper_confirm
Idempotent

Mint the exam paper from a job parked at awaiting_confirmation (created via paper_create). Materialises the ExamPaper, questions, and mark schemes from the extraction draft, synchronously. Optionally override the detected identity (title/subject/board/year); omit to use what extraction detected. Idempotent — confirming an already-committed job returns its paper. Returns the exam_paper_id.

Input Schema

NameRequiredDescriptionDefault
job_idYesID of the ingestion job to confirm. Must be parked at awaiting_confirmation (poll ingestion_get first).
metadataNoOptional identity overrides. Omit to mint the paper with the identity detected during extraction. `total_marks` is always derived from the question marks — never supplied here.

Output Schema

NameRequiredDescriptionDefault
statusYesTerminal status of the paper (complete).
outcomeYes"created" on first confirm, "already committed" on re-confirm.
view_withYesThe tool to inspect the paper with (paper_get).
exam_paper_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changed
    • removedInput schema / properties / metadata / properties / year_group
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Override the detected class / year group."
-}
  3. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. Changed1 schema field changed
    • addedInput schema / properties / metadata / properties / assessment_date
      Added value: +{
+  "anyOf": [
+    {
+      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "When this cohort SAT the paper, as YYYY-MM-DD. Never detected — it is a fact about a school, not about the paper — so it is only ever set here. Omit when nobody has said."
+}
  5. First observed

TDQS

A4.1/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 reinforces idempotency with concrete semantics ('confirming an already-committed job returns its paper'). It also discloses that materialisation is synchronous, which is real operational context the annotations cannot express. It stops short of saying what happens to the extraction draft after minting or how a wrong-state job fails.

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?

Four tight sentences, front-loaded with the action and precondition, each carrying information. The closing 'Returns the exam_paper_id' is slightly redundant given an output schema exists, but it costs little.

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 a rich annotation set, 100% schema coverage and an output schema, the description covers the operation's key facts: prerequisite job state, synchronous materialisation, override/omit behavior, and idempotency. The remaining gap is failure and side-effect behavior — what happens to the draft or the job on success, and what an unsatisfied precondition yields.

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 schema already documents job_id, every override field, the subject enum, and the assessment_date caveat. The description only restates the override group at a high level ('optionally override the detected identity (title/subject/board/year)'); it notably omits assessment_date from that list and adds no formatting detail beyond the schema.

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?

States a specific verb and resource — mint an ExamPaper from a job at awaiting_confirmation — and names the entities produced (ExamPaper, questions, mark schemes). It also anchors itself against paper_create (the producer of the job) and paper_get (the reader), so an agent can route without opening schemas.

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 the precondition (job must be parked at awaiting_confirmation, created via paper_create) and the override rule: supply metadata to override, omit to inherit what extraction detected. It does not explicitly say what to do if the job is not yet parked, or point at a specific alternative for reading a paper instead.

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

All DeepMark toolsInspect
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