RidgeHQAPP

Assign instructors to a session

assign_instructors_to_session

Idempotent

Assign or replace the instructors on an existing session, e.g. 'put Alex on tomorrow's 10am dive instead of Sam'. Replaces the full instructor list for the session (pass every instructor who should remain assigned, not just the one being added). MEDIUM RISK — always show a confirmation prompt before executing. Checks for instructor double-booking the same way the Event Planner UI does. Audited and reversible. Medium risk. The first call returns confirm_required with an action_id; call again with confirmed_action_id set to it to execute.

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": {
      "session_id": "<session_id>",
      "instructor_ids": "<instructor_ids>"
    },
    "name": "assign_instructors_to_session"
  }
}

Input Schema

Name	Required	Description
`reason`	No	Optional reason for the change (for audit log)
`session_id`	Yes	UUID of the session to update
`instructor_ids`	Yes	Full list of instructor UUIDs that should be assigned to the session after this call
`confirmed_action_id`	No	Set to the action_id from the confirm_required response to execute this action. Omit on the first call.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 3, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: MEDIUM RISK level, mandatory confirmation prompt, a double-booking check mirroring the Event Planner UI, audit logging, reversibility, and the two-step confirm_required/action_id flow. None of this is derivable from readOnlyHint/idempotentHint/destructiveHint.

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?

Front-loads the core purpose and the replace semantics, then the safety/flow details. It is efficient overall, though 'MEDIUM RISK' and 'Medium risk' are stated twice, which is minor redundancy.

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

Completeness5/5

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

For a mutation tool with no output schema, the description supplies everything an agent needs: what changes, the full-list replacement rule, the double-booking guard, the risk level, and the exact two-call confirmation protocol. Nothing material 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 description coverage is 100%, so the schema already documents all four parameters including the full-list semantics of instructor_ids and the confirmed_action_id flow. The description reinforces the replace behavior but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb (assign/replace) and resource (instructors on a session), and clearly distinguishes itself from the sibling assign_participant_to_session by naming instructors rather than participants. The worked example ('put Alex on tomorrow's 10am dive instead of Sam') makes the replace semantics unambiguous.

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 clear context for use plus a critical 'pass every instructor who should remain assigned, not just the one being added' warning that prevents the most likely misuse. It does not explicitly name an alternative tool for the additive case, so it falls short of a 5.

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

All RidgeHQAPP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?