Skip to main content
Glama

One class

studentvue_class
Read-only

Retrieve one class's assignments, scores, due dates, categories, and missing-work flags from a student's grade book using part of the class name. Read-only.

Instructions

One class's assignments from the grade book, with scores, due dates and categories (missing work is marked). Give part of the class name, e.g. 'CALCULUS'. Read-only.

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": {
      "class": "<class>"
    },
    "name": "studentvue_class"
  }
}

Input Schema

NameRequiredDescriptionDefault
classYesPart of the class name as it appears in the grade book

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description's 'Read-only.' merely restates that. It does add real behavioral detail beyond the annotations — that missing work is flagged and that name matching is by substring — but says nothing about what happens on ambiguous or no matches.

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?

Three short sentences, front-loaded with the return payload before the calling convention. The only near-waste is 'Read-only.', which repeats the annotation, though it is cheap enough not to hurt scanning.

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 one-parameter read tool with a full schema and no output schema, describing the returned fields and the missing-work marking is close to sufficient. The remaining gap is match behavior on partial names, which an agent would want before calling.

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 schema already states 'Part of the class name as it appears in the grade book', so the description's wording largely duplicates it. The 'CALCULUS' example adds a small amount of concreteness about partial matching, which is the baseline for a fully documented single parameter.

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: one class's assignments from the grade book, enumerating what comes back (scores, due dates, categories, missing-work markers). It is clearly narrower than studentvue_gradebook, but it never names that sibling or explicitly contrasts the two.

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 — the reader infers this is the per-class drill-down, and the 'give part of the class name' line tells how to call it but not when to prefer it over the gradebook tool. No exclusions or alternative-routing guidance is given.

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