Skip to main content
Glama

Get status

get_status
Read-onlyIdempotent

The checklist: what is received, what is missing, and the next action in plain words.

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": {
      "school": "<school>",
      "application_id": "<application_id>",
      "application_token": "<application_token>"
    },
    "name": "get_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
schoolYesThe school's slug from list_schools, e.g. "vvs"
application_idYes
application_tokenYesThe application_token returned by verify_email for this school

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine context beyond that: it discloses the shape of the result (received vs. missing items plus a plain-language next action), which matters because there is no output schema. It stops short of noting auth requirements beyond the token, but the added value is real.

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 no wasted words, and the result-oriented framing is front-loaded. It is slightly elliptical ('The checklist' has no stated antecedent), but the economy is appropriate.

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 output schema, the description does the minimum expected by sketching the return content, which is the right instinct. But for a three-required-parameter tool tied to an application workflow, it says nothing about the parameters, prerequisites, or how the 'next action' should be acted on, leaving meaningful gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 67%, and application_id carries no description at all, so the schema does not fully carry the burden. The description mentions no parameters whatsoever — not the school slug, not the application_id, not the verify_email-issued token — so it adds zero meaning beyond the structured fields where they exist and fails to compensate for the undocumented one.

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

Purpose3/5

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

The description conveys what the tool returns — a checklist of what is received, what is missing, and the next action — which implies an application-completeness check. However, it never names the resource (an application status) or uses a verb, so the agent must infer from the required application_id/application_token parameters that this reports on an application. No sibling is named or differentiated.

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 guidance on when to call this versus siblings such as get_school_instructions, submit_application, or update_application. The phrase 'next action' hints that this is a diagnostic/entry point, but no condition or exclusion is stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.