Skip to main content
Glama

get_submission_status

Check the submission status of a specific Canvas assignment using course and assignment IDs to confirm whether work was submitted.

Instructions

Check submission status for a specific assignment

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": {
      "course_id": "<course_id>",
      "assignment_id": "<assignment_id>"
    },
    "name": "get_submission_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYesCanvas course ID
assignment_idYesAssignment ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. 'Check' implies a read operation, but the description says nothing about required permissions, what happens when no submission exists, or what status values are returned, leaving meaningful behavioral gaps for a read tool with zero annotation coverage.

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?

A single front-loaded sentence with no wasted wording; the resource and scope appear immediately. Its brevity is efficient, though it borders on under-specification rather than tightness.

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?

This is a simple two-parameter read tool with fully documented parameters and no output schema, so the description need not explain return values. However, with no annotations and no output schema, the agent gets no sense of what a 'status' response contains or how missing submissions are represented, which is a real gap for a status-checking tool.

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% — both course_id and assignment_id are documented as Canvas course ID and assignment ID — so the baseline 3 applies. The description adds only the framing that assignment_id scopes to one specific assignment and does not extend the schema's meaning.

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?

The description states a specific verb ('Check') plus resource ('submission status') and restricts scope to 'a specific assignment', so an agent knows exactly what it retrieves. It does not differentiate from siblings such as get_assignments or get_grades, which is the only thing keeping it from a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative. The agent must infer from the name alone whether this is the right tool versus get_grades or get_assignments, and there is no mention of prerequisites such as needing an existing submission.

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