Skip to main content
Glama

Missing and late assignments

get_missing
Read-onlyIdempotent

Retrieves assignments flagged missing or late across all current-term classes for a student, consolidating outstanding work into one list.

Instructions

Every assignment flagged missing or late across all classes in the current term. Loads each class once, so it can take several seconds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_missing"
  }
}

Input Schema

NameRequiredDescriptionDefault
studentNoStudent to use: name, or index from list_students. Defaults to PS_DEFAULT_STUDENT, else the student PowerSchool shows.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive traits, so the bar is lower. The description still adds real value beyond them by disclosing the per-class loading pattern and the multi-second latency, plus the term scoping constraint. It stops short of describing the return shape or any truncation behavior.

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?

Two sentences, zero waste, and front-loaded with the scope before the performance caveat. Every clause earns its place.

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?

For a read-only, single-optional-parameter tool the description covers scope and latency adequately. Because there is no output schema, it could have specified what each returned assignment entry contains, which is the one remaining gap.

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 coverage is 100% and the single 'student' parameter is fully documented in the schema, so baseline 3 applies. The description adds no meaning about the parameter; 'across all classes' slightly obscures that results are scoped to the selected student rather than truly global.

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 resource and scope: 'Every assignment flagged missing or late across all classes in the current term.' An agent can tell this apart from get_grades or get_class_scores by the 'missing or late' qualifier, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is only implied by the described output (find missing/late work). There is no explicit when-to-use statement, no when-not-to-use, and no pointer to an alternative such as get_class_scores for per-assignment detail.

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