Skip to main content
Glama

Verify the parent's email

verify_email

Checks the 6-digit code. Returns the application_token; store it in the family's folder as .admit-protocol/.token and never print it.

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>",
      "code": "<code>"
    },
    "name": "verify_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
schoolYesThe school's slug from list_schools, e.g. "vvs"
application_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Adds meaningful behavior beyond annotations: it discloses that a token is returned and gives a handling rule (store at .admit-protocol/<school>.token, never print). However, with readOnlyHint=false and idempotentHint=false declared, it does not explain what changes on the server, whether retries after a wrong code are permitted, or any attempt/rate limits.

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?

Two sentences, zero waste, front-loaded with the action and immediately followed by the return value and the security-critical handling instruction.

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 3-param non-idempotent tool with no output schema, the description covers the return value and secret handling well. The remaining gap is failure behavior and prerequisite context, both of which matter but are secondary to correct invocation.

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 33%, so the description should compensate; it does partially by clarifying that `code` is the 6-digit value, but `application_id` gets no explanation in description or schema, and its origin (from start_application) is left for the agent to infer.

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 action and resource: checks a 6-digit code (verifying the parent's email) and issues an application_token. That is clearly distinct from siblings like resend_code or start_application, though the description never names an alternative to reinforce the boundary.

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?

No explicit when-to-use guidance, no prerequisites (e.g. that an application must exist via start_application), and no pointer to resend_code when the code never arrives. Only the weak implication that this runs after a code has been received.

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.