Skip to main content
Glama

Update application fields

update_application
Idempotent

Changes student or entering details. The verified parent email cannot be changed.

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>",
      "patch": "<patch>"
    },
    "name": "update_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
patchYes
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

C2.7/5.0
Behavior3/5

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

The annotations already cover the safety profile: non-read-only, non-destructive, idempotent, and closed-world. The description adds an important behavioral constraint that the verified parent email is immutable, but it does not explain partial-update behavior, patch merge semantics, or failure modes.

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?

The description is two short sentences with no wasted text, and the immutable-field constraint is stated directly. The first sentence is ambiguous, but the overall definition is appropriately compact rather than bloated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with four required parameters, a nested free-form patch object, 50% schema coverage, and no output schema, the description is substantially incomplete. It should explain what fields can be updated, how the patch object is interpreted, and what errors occur when a forbidden field is included.

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 description coverage is only 50%, and the most important parameter, the free-form nested patch object, has no description in either the schema or the tool description. The description only clarifies that parent email cannot be changed, leaving application_id, patch structure, and allowed patch keys unexplained.

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 verb "Changes" signals a mutation and the title identifies the resource as an application, but "student or entering details" is vague and awkwardly worded. It does not clearly define the scope of updatable fields or distinguish this tool from siblings such as start_application or submit_application.

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?

The description gives no explicit guidance on when to use update_application rather than sibling tools such as submit_application or withdraw. The only constraint mentioned is that the verified parent email cannot be changed, which is useful but does not explain when or why to call this tool.

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.