Skip to main content
Glama

Start an application

start_application

Creates a draft application at the named school and emails a 6-digit code to the parent or guardian. The application object must match that school's schema (get_school_instructions). Read the payload back to the family before calling this.

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": "<application>"
    },
    "name": "start_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
schoolYesThe school's slug from list_schools, e.g. "vvs"
applicationYesThe application body, per the school's schema

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare that this is a non-read-only, non-idempotent, non-destructive write; the description adds materially more by disclosing the email side effect, the draft (not submitted) state, and the schema-conformance requirement. It does not mention what happens if the code expires, whether repeated calls create duplicate drafts, or what the call returns, which keeps it below 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, each carrying distinct load: purpose and side effect first, then the schema prerequisite, then the human verification step. No filler or redundant restatement of the title.

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 two-parameter write with a nested free-form payload and no output schema, the description covers what is created, the outbound email, and the prerequisite schema source. It leaves the return value and duplicate-draft behavior unstated, but nothing needed to attempt a correct call 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?

Schema coverage is 100%, so the slug format for 'school' and the free-form shape of 'application' are already documented. The description adds the useful pointer to get_school_instructions for the nested payload shape, but gives no detail on the allowed fields inside the application body, which is the riskiest part of the call.

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?

States a specific verb and resource ('Creates a draft application at the named school') plus the immediate side effect (emails a 6-digit code). The word 'draft' implicitly separates it from submit_application, but no sibling is named explicitly, so the differentiation is inferred rather than declared.

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?

Gives a concrete prerequisite (the application object must match the school's schema, obtained via get_school_instructions) and a pre-call workflow step (read the payload back to the family). It stops short of saying when not to use it, e.g. when a draft already exists or when the family should use update_application instead.

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.