Skip to main content
Glama

studentfirst_leave_applications

Read-only

Lists your StudentFirst leave applications with dates and status so you can review submitted leave; it does not submit new leave requests.

Instructions

List your StudentFirst leave applications with dates and status. Use when the user asks about leave they applied for. This tool does not apply for leave; the user does that on the StudentFirst website.

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

Input Schema

NameRequiredDescriptionDefault
accountNoSaved account to use (see learnjcu_list_accounts). Only needed when several accounts are saved and the user has not chosen one yet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

The readOnlyHint=true and openWorldHint=true annotations already establish this as a safe read operation, and the description largely reinforces that by stating it does not perform the application action. It adds the returned fields (dates and status), but says nothing about authentication/session state, history range, or completeness of the list, so it only modestly exceeds the annotations.

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, front-loaded with the operation and return content, followed by usage context and a scope boundary. Every sentence earns its place with no filler.

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 single-optional-parameter list tool with no output schema and annotations covering the safety profile, the description covers purpose, usage trigger, returned fields, and the key non-behavior (cannot apply). Only minor gaps remain, such as authentication prerequisites implied by openWorldHint.

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% and the single optional 'account' parameter is well documented, including a pointer to learnjcu_list_accounts and the condition for supplying it. The description itself adds nothing about parameters, so baseline 3 applies.

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 clear verb and resource ('List your StudentFirst leave applications') plus the returned content ('dates and status'), which is enough for an agent to identify the operation. It does not differentiate itself by naming sibling tools such as studentfirst_status or studentfirst_overview, so it falls short of a 5.

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?

'Use when the user asks about leave they applied for' gives a concrete when-to-use condition. It also sets a boundary ('This tool does not apply for leave'), effectively a when-not. It does not name an alternative sibling to route to, but the usage context is clear.

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