Skip to main content
Glama

List students

list_students
Read-onlyIdempotent

Retrieves students on the PowerSchool account, returning each index for the student argument and marking which student is active in the portal.

Instructions

Students on the PowerSchool account, with the index to pass as the student argument. active marks the student whose grade pages the portal is showing.

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": "list_students"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's job is to add context, which it does: it discloses that the result is a list of students tied to the account and that one entry is flagged `active` for the grade pages currently being viewed. It does not state ordering, whether the list is ever truncated, or what happens when no student is active, which is a meaningful gap for an open-world read.

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?

Two short sentences, no filler, and the key point (the index for the `student` argument) comes first. The fragmentary opening without a verb and the terse `active` clause cost a point in readability, but nothing is wasted.

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 zero-parameter read tool with no output schema, the description must carry the return-shape burden, and it only partly does: it says an index exists but never names the field or the other per-student fields returned, and gives no guidance on calling it before versus after session_status. Adequate but with clear gaps for an open-world listing tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero input parameters the baseline is 4. The description goes beyond that by explaining the cross-tool contract — the returned index is the value expected by the `student` argument elsewhere — which is real semantic value not present in this tool's own schema.

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 the specific resource (students on the PowerSchool account) and, unusually, states the utility of the result: the index to pass as the `student` argument. It is a noun phrase rather than a verb+resource statement, and it never names a sibling, but an agent can still tell this is the roster-discovery tool that feeds the grade-oriented siblings.

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 saying the output index is passed as the `student` argument, it hints that this should be called before per-student tools like get_grades or get_class_scores. There is no explicit when-to-use, no exclusion, and no mention of prerequisites such as an authenticated session, which the session_status sibling implies matters here.

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