Skip to main content
Glama

PowerSchool session status

session_status
Read-onlyIdempotent

Check PowerSchool login status, remaining idle time, and active student; if logged out, instruct the user to run ps-login. Does not extend the session.

Instructions

Whether the PowerSchool login is alive, how many seconds of idle time remain, and which student is active. When logged out, tell the user to run ps-login on their PC. Does not extend the session.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description still adds genuine value beyond them by disclosing that the call is non-extending (a common wrong assumption) and by specifying the logged-out remediation path. It does not describe return field shapes or behavior near the idle timeout, which are the remaining unknowns.

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 plus a constraint, front-loaded with what is reported. Every clause carries information an agent would otherwise have to guess. Minor deduction for the slightly compressed first sentence, which reads as a fragment rather than a stated verb.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no parameters, so the description must carry the return semantics itself, and it does: liveness, remaining idle seconds, active student. Combined with annotations covering the safety profile and the explicit non-extending caveat, an agent has everything needed to call and interpret this 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; per the baseline rule this scores 4. The schema is an empty object, consistent with a pure status read.

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 (PowerSchool login/session) and the three things it reports: liveness, seconds of idle time remaining, and the active student. That is far more specific than a restatement of the name. It does not explicitly contrast with siblings, but its reporting role is plainly distinct from the grade/attendance data tools, so the missing sibling reference costs little.

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?

It gives a clear use context (checking login liveness before proceeding) and an explicit when-not: 'Does not extend the session,' which stops an agent from calling it to refresh a session. It also supplies remediation for the logged-out case (tell the user to run ps-login on their PC). What is missing is an explicit statement of when to prefer it over simply attempting a data call and handling failure.

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