Skip to main content
Glama

Submit

submit_application
Idempotent

Hands the application to the school. Needs the student's identity and the required writing. Items can still be added afterwards.

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

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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false; the description adds genuinely useful state context beyond that – that the application is not sealed on submission and items may still be added. It does not explain what happens to the application_token, what an error looks like, or whether re-submitting is safe, despite idempotentHint being the most consequential annotation here.

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?

Three short sentences, front-loaded with the action, then prerequisites, then post-condition. No filler, though "Hands the application to the school" costs a beat of interpretation that a direct verb would not.

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?

For a mutating, token-gated submission with no output schema, the description covers prerequisites and the post-submission state, which are the two most important unknowns. It still leaves the outcome of a successful call (status change? confirmation payload?) unspecified, so an agent cannot predict the result shape.

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?

The description never names or explains school, application_id, or application_token; "the student's identity and the required writing" gestures at prerequisites without mapping to any parameter. With schema coverage at 67%, the undocumented application_id receives no compensating explanation, so the description adds little semantic value here.

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?

"Hands the application to the school" identifies the action as a final submission of an existing application, which separates it from siblings like start_application and update_application. The phrasing is metaphorical rather than a direct verb+resource statement, so an agent must map "hands ... to the school" onto "submit", but the intent is recoverable.

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?

"Needs the student's identity and the required writing" states prerequisites, and "Items can still be added afterwards" signals you need not wait for a complete application before submitting. However, no alternative tool is named and there is no explicit when-not guidance (e.g., after withdraw, or before verify_email).

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.