Skip to main content
Glama

submission_status

Retrieve the submission and grading status for one assignment using its assignid from list_assignments to check whether work was submitted and graded.

Instructions

Submission/grading status of one assignment (use the assignid from list_assignments).

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": {
      "assignid": "<assignid>"
    },
    "name": "submission_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
assignidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the entire behavioral burden and does little with it: it never states that this is a read-only lookup, what permission or enrollment context is required, or whether it exposes other students' data. Neither the return shape nor the set of possible status values is described, and there is no output schema to fall back on.

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?

One compact sentence that front-loads the resource and scopes it immediately, with the argument hint placed in parentheses so it does not interrupt the core statement. There is no filler, though the phrasing is telegraphic to the point of omitting a verb.

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?

For a single-parameter read tool with no annotations and no output schema, the definition covers what the tool is and where the argument comes from, which is the minimum viable set. It leaves the agent guessing about return contents (per-student breakdown? grade, submission timestamp, late flag?) and does not clarify whether calling it without a submission returns an error or an empty status.

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 0% for the single assignid parameter, so the description must supply the meaning — and it does add real value by specifying that the id comes from list_assignments. It adds nothing about type, valid range, or behavior on an invalid/unenrolled id.

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 names a specific resource pair ('submission/grading status') scoped to 'one assignment', which is enough for an agent to distinguish it from siblings like list_assignments or upcoming_deadlines. The verb is only implied ('status of'), so it reads more like a noun phrase than an action, but the intent 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?

The parenthetical '(use the assignid from list_assignments)' gives an explicit prerequisite and routes the agent to the correct sibling for obtaining the argument, which is genuinely actionable workflow guidance. It stops short of stating when to prefer this over other status-like tools or what happens for an ungraded/missing submission, so it is not a full when/when-not treatment.

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