Skip to main content
Glama

sis_other_applications

Retrieve Westlake University application statuses for student-status changes, hardship determinations, undergraduate-to-doctoral transitions, and employment.

Instructions

取学籍异动流程 / 困难认定 / 本博衔接 / 就业四类申请状态。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. The verb 取 implies a read-only operation, but the description never states whether it queries a live service, needs authentication, or returns one aggregate record versus four separate statuses. For a zero-parameter read this is modest but real added context.

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?

A single short sentence with the action front-loaded and the four categories listed compactly. Nothing is wasted, though the slash-delimited enumeration reads more like a label than explanatory prose.

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?

With no annotations and no output schema, the description is the only documentation. It identifies the four covered categories but does not say whether all four are returned together, what a status field looks like, or how the result is shaped — details an agent needs to use the output correctly.

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 no parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the enumeration of the four request categories at least tells the agent what the fixed scope of the call is.

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 gives a specific verb (取/fetch) and a specific resource (申请状态/application status), then enumerates the four categories covered: 学籍异动流程, 困难认定, 本博衔接, 就业. This is far more specific than the bare tool name, though it never contrasts itself with the similarly-named sibling sis_statuses, so an agent still has to guess which one covers what.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus alternatives, no prerequisites, and no exclusion. The presence of a sibling named sis_statuses makes the omission costly, since an agent has no basis for choosing between them.

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