Skip to main content
Glama

Final grades

get_final_grades
Read-only

Get midterm, predicted and annual grades per subject as the school published them. A column the school does not show is unavailable; an empty or - raw value is not given yet. For individual grades use get_grades or get_grades_window.

Instructions

Get midterm, predicted and annual grades per subject as the school published them. A column the school does not show is unavailable; an empty or - raw value is not given yet. For individual grades use get_grades or get_grades_window.

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": {
      "account_alias": "<account_alias>"
    },
    "name": "get_final_grades"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_aliasYesLogin alias from list_accounts.

Output Schema

NameRequiredDescriptionDefault
itemsYes
identityYes
paginationNo
observationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.8.1
    • removedOutput schema / $defs / GradeSummaryValue / description
      Removed value: -"Column presence, separate from its raw school-provided value.\n\nUnavailable columns have raw=None. Available columns preserve empty strings,\nunassigned markers such as '-', symbols, and descriptive values without\ninventing numeric conversions or dates."
    • changedOutput schema / $defs / Observation / properties / observed_at / pattern
      Previous value: -"^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}(?:\\.[0-9]{1,6})?(?:Z|[+-][0-9]{2}:[0-9]{2})?$"New value: +"^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}(\\.[0-9]{1,6})?(Z|[+-][0-9]{2}:[0-9]{2})?$"
  2. Changed2 schema fields changedv2.5.0
    • removedOutput schema / $defs / Pagination / additionalProperties
      Removed value: -false
    • removedOutput schema / additionalProperties
      Removed value: -false
  3. Changed1 schema field changedv2.3.1
    • changedInput schema / properties / account_alias / pattern
      Previous value: -"^(?:[^\\s\\x00-\\x1f\\x7f]|[^\\s\\x00-\\x1f\\x7f](?:[^\\s\\x00-\\x1f\\x7f]| )*[^\\s\\x00-\\x1f\\x7f])$"New value: +"^[^\\s\\x00-\\x1f\\x7f](?: *[^\\s\\x00-\\x1f\\x7f])*$"
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful data semantics beyond that: unavailable columns, and that an empty or '-' raw value means the grade isn't published yet — this prevents the agent from misreporting missing data as a zero. No permission or freshness/caching notes, so not a 5.

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?

Three short sentences: purpose first, data caveats second, alternative routing last. Every sentence carries information an agent needs and nothing is repeated from the schema or annotations.

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?

An output schema exists, so return values needn't be explained, and annotations cover the read-only profile. For a single-parameter read tool the description covers purpose, data interpretation quirks, and sibling routing — nothing material is missing.

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?

There is one parameter with 100% schema description coverage ('Login alias from list_accounts.'), so the schema already carries the meaning and the baseline is 3. The description adds nothing about account_alias — no note on whether it identifies the student or the parent account, which is the one ambiguity worth clarifying here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get midterm, predicted and annual grades per subject') plus a scoping qualifier ('as the school published them'). The final sentence names the sibling tools it is not, so an agent can distinguish it from get_grades without opening either schema.

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 explicitly routes the agent elsewhere for individual grades ('For individual grades use get_grades or get_grades_window'), which functions as both an alternative and an implicit when-not. It doesn't spell out edge cases such as an account with no published final grades or how it relates to get_school_year_archive, so it falls short of a full when/when-not treatment.

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