Skip to main content
Glama

Other pages

studentvue_page
Read-only

Fetches a chosen StudentVue page as text—attendance, schedule, calendar, report card, messages, or student info—to give AI assistants read-only portal data.

Instructions

Another StudentVue page as text: attendance, schedule, calendar, report_card, messages or student (student info). 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": {
      "page": "<page>"
    },
    "name": "studentvue_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes the safe read-only profile, and the description repeats 'Read-only' while adding that results are returned 'as text'. It does not add other behavioral context such as error behavior or data scope, so the value beyond annotations is modest.

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 description is a single front-loaded sentence with no wasted wording. It gives the return format and the complete page list immediately.

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 simple one-parameter read-only tool with no output schema, the description covers the return format and all page choices. It is almost complete, with the only gap being explicit routing guidance versus the two sibling tools.

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?

Schema description coverage is 0%, so the description must carry parameter meaning. It fully lists the allowed page values and clarifies that 'student' means student info, adding useful semantics beyond the bare enum.

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 that the tool returns 'Another StudentVue page as text' and enumerates the supported pages, making the resource and scope clear. It does not explicitly name the sibling tools studentvue_class or studentvue_gradebook as alternatives, so differentiation is only implicit.

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?

The enumerated page values imply when this tool is used, but the description never states when to choose it over studentvue_class or studentvue_gradebook. There are no explicit exclusions or alternative-routing instructions.

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