Skip to main content
Glama

Resend the code

resend_code
Idempotent

Sends a new 6-digit code to the parent's email.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false, idempotentHint=true), so the description's real contribution is that a code is emailed to the parent and is 6 digits. It omits meaningful side effects: whether a previously issued code is invalidated, and any rate limiting or cooldown on repeated resends — which is notable given idempotentHint=true sits awkwardly with 'sends a new code' each call.

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 front-loaded sentence with no filler. Its brevity is efficient rather than padded, though the same brevity leaves behavior under-specified elsewhere.

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?

This is a side-effecting operation that sends external email with two required parameters and no output schema, yet the description covers only the mechanical action. Prerequisites, effect on prior codes, and resend limits — the things an agent most needs before calling — are absent.

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 50%: school is documented but application_id is only a UUID format constraint with no explanation. The description mentions neither parameter, so it fails to compensate for the undocumented application_id, which is required and whose role (which application's parent email receives the code) is left implicit.

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: sends a new 6-digit code to the parent's email. An agent can tell this generates a fresh verification code rather than checking one, though the description never names the related sibling verify_email to draw the contrast explicitly.

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 guidance on when to call this versus verify_email, or on prerequisites such as the application existing or the email still being unverified. The agent must infer the 'code expired / never arrived' scenario entirely on its own.

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.