Skip to main content
Glama

Teacher comments

get_teacher_comments
Read-onlyIdempotent

Retrieve teacher comments for each class in a reporting term, optionally for a specific student. Returns an empty result when teachers have not written comments.

Instructions

Teacher comments per class for a reporting term (empty when teachers have not written any).

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_teacher_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
termNoGrade column such as S1 or P2. Default: the portal's current term
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.6/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds useful behavioral detail that results are empty when teachers have not written comments, but it does not describe return structure, permissions, or other operational characteristics.

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?

The definition is a single front-loaded sentence with no wasted wording. The parenthetical empty-result note is concise and earns its place by clarifying behavior.

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 low-complexity, two-parameter read tool with rich annotations and full schema coverage, the description is largely sufficient. It could add slightly more clarity about whether the result is a per-class mapping, but the core behavior is adequately conveyed.

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 the term and student parameters, including defaults. The description does not add syntax, format, or additional meaning beyond what the schema provides.

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 resource, 'teacher comments', and scopes it to per-class comments for a reporting term, including the empty-result condition. It is clearly distinct in substance from score/grade siblings, but it does not explicitly contrast itself with alternatives such as get_grades or get_class_scores.

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 implied by 'for a reporting term' and the comments-specific resource, but the description gives no explicit when-to-use guidance, exclusions, or alternatives. An agent can infer it should use this for teacher comments rather than grades, but the routing guidance is not spelled out.

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