Skip to main content
Glama
chrischall

alphaportal-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

alphaportal_edit_walk_radius

Destructive

Set a student's walk-zone radius in meters to update transportation eligibility, with confirmation before changes take effect.

Instructions

Set a student's walk-zone radius, in meters. This can affect transportation eligibility, so it asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview of the exact payload and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Verified required fields: studentId, radius.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
studentIdYesThe numeric studentId.
confirmTokenNoONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.
radiusMetersYesWalk-zone radius in meters (the API stores the base-unit distance).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.0
    • removedInput schema / properties / confirm
      Removed value: -{
-  "description": "Must be true to proceed. Without this, the tool returns a preview.",
-  "type": "boolean"
-}
    • addedInput schema / properties / confirmToken
      Added value: +{
+  "description": "ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 \"confirmation-required\" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.",
+  "type": "string"
+}
  2. Changed1 schema field changedv0.4.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv0.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the mutation/safety profile is covered. The description adds valuable behavioral context: it can affect transportation eligibility, it triggers a confirmation prompt where supported, and otherwise the first call returns a preview plus confirmToken, and only a repeat call with that token proceeds. This goes beyond the annotations. Minor gap: it doesn't state whether the operation is reversible or what happens after confirmation, but the core behavior is well disclosed.

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?

The description is compact and well-structured: a single opening sentence stating the purpose, followed by a focused explanation of the confirmation flow and a 'Verified required fields' line. Every sentence earns its place, and the most important behavioral detail (confirmation requirement) is front-loaded.

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?

Given the tool's complexity (confirmation modes, token flow) and that there is no output schema, the description explains the two-step fallback thoroughly enough for an agent to understand the flow. It could add what the confirmation-required response looks like or what the final response returns, but the essential call pattern is clear: first call previews, second call with confirmToken proceeds. It is complete enough for 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 description coverage is 100%, so the schema fully documents all three parameters and their constraints, including the special usage rules for confirmToken. The description adds the clarification that verified required fields are studentId and radius, and that the API stores the base-unit distance (echoing the schema's radiusMeters description). It does not add new syntax or format details beyond the schema, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Set'), a specific resource ('a student's walk-zone radius'), and the unit ('in meters'). It clearly differentiates this from sibling tools, which are mostly read-only getters/listers; the only other 'set' sibling, alphaportal_set_notification, has a different resource. The description also mentions a key effect (transportation eligibility), adding clarity beyond the tool name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use it (to set a student's walk-zone radius) and explicitly describes the confirmation workflow: a prompt for clients that support elicitation, or a two-step token flow otherwise. It warns about the effect on transportation eligibility, implying caution. It does not explicitly name an alternative tool, but the context signals show only one other 'set' tool with a different resource, so the usage guidance is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools