RxRooster

Prepare an anesthesia service draft

prepare_anesthesia_service_draft

Read-onlyIdempotent

Use when a CRNA, SRNA, or anesthesiologist wants to structure their own work terms for RxRooster review. Ask only the returned next_question and its options, carry known facts forward, and preserve skipped optional fields; never enumerate missing_fields or preview later questions. Use multi-select only when returned. Do not include identity or contact data. This tool creates no service record and does not save or publish.

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": {
      "provider_type": "<provider_type>"
    },
    "name": "prepare_anesthesia_service_draft"
  }
}

Input Schema

Name	Required	Description
`state`	No	US state name or two-letter postal code.
`area_query`	No	City, metro, or public service-area label, without an address.
`work_types`	No
`days_of_week`	No
`radius_miles`	No	Approximate service radius; 3000 represents nationwide travel.
`provider_type`	Yes	The provider credential or training path stated by the user.
`contract_types`	No
`call_preference`	No	Explicit call preference: any means no restriction, no_call excludes call work, and call_ok means call is acceptable but not necessarily preferred.
`rate_visibility`	No
`availability_end`	No	Calendar date in YYYY-MM-DD format.
`shift_preferences`	No
`availability_start`	No	Calendar date in YYYY-MM-DD format.
`minimum_hourly_rate`	No
`shift_lengths_hours`	No
`minimum_annual_salary`	No
`skipped_optional_fields`	No	Optional provider-service fields the user explicitly chose to skip. Preserve and resend them on later calls so the stateless guided intake advances without translating unknown into no.

Output Schema

Name	Required	Description	Default
`draft`	Yes
`status`	Yes
`privacy`	Yes
`benefits`	Yes
`next_step`	Yes
`generated_at`	Yes
`next_question`	Yes
`provider_path`	Yes
`missing_fields`	Yes
`schema_version`	Yes
`draft_fingerprint`	Yes
`skipped_optional_fields`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 30, 2026

addedInput schema / properties / skipped_optional_fields

Added value: +{
+  "description": "Optional provider-service fields the user explicitly chose to skip. Preserve and resend them on later calls so the stateless guided intake advances without translating unknown into no.",
+  "items": {
+    "enum": [
+      "contract_types",
+      "schedule_preferences",
+      "radius_miles"
+    ],
+    "type": "string"
+  },
+  "maxItems": 3,
+  "type": "array"
+}

addedOutput schema / properties / next_question

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "fallback_instruction": {
+          "type": "string"
+        },
+        "field": {
+          "type": "string"
+        },
+        "options": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "label": {
+                "type": "string"
+              },
+              "value": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "value",
+              "label"
+            ],
+            "type": "object"
+          },
+          "maxItems": 12,
+          "type": "array"
+        },
+        "prompt": {
+          "type": "string"
+        },
+        "required_for_handoff": {
+          "type": "boolean"
+        },
+        "response_kind": {
+          "enum": [
+            "free_text",
+            "single_select",
+            "multi_select",
+            "number",
+            "date",
+            "confirmation"
+          ],
+          "type": "string"
+        },
+        "skippable": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "field",
+        "prompt",
+        "response_kind",
+        "options",
+        "required_for_handoff",
+        "skippable",
+        "fallback_instruction"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / skipped_optional_fields

Added value: +{
+  "items": {
+    "enum": [
+      "contract_types",
+      "schedule_preferences",
+      "radius_miles"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "schema_version",
-  "generated_at",
-  "status",
-  "provider_path",
-  "draft",
-  "missing_fields",
-  "draft_fingerprint",
-  "privacy",
-  "benefits",
-  "next_step"
-]New value: +[
+  "schema_version",
+  "generated_at",
+  "status",
+  "provider_path",
+  "draft",
+  "missing_fields",
+  "next_question",
+  "skipped_optional_fields",
+  "draft_fingerprint",
+  "privacy",
+  "benefits",
+  "next_step"
+]

Changed3 schema fields changedOct 21, 2026

addedInput schema / properties / call_preference

Added value: +{
+  "description": "Explicit call preference: any means no restriction, no_call excludes call work, and call_ok means call is acceptable but not necessarily preferred.",
+  "enum": [
+    "any",
+    "no_call",
+    "call_ok"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / draft / properties / call_preference

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "any",
+        "no_call",
+        "call_ok"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / draft / required

Previous value: -[
-  "provider_type",
-  "area_query",
-  "state",
-  "radius_miles",
-  "availability_start",
-  "availability_end",
-  "days_of_week",
-  "shift_preferences",
-  "shift_lengths_hours",
-  "work_types",
-  "contract_types",
-  "minimum_hourly_rate",
-  "minimum_annual_salary",
-  "rate_visibility"
-]New value: +[
+  "provider_type",
+  "area_query",
+  "state",
+  "radius_miles",
+  "availability_start",
+  "availability_end",
+  "days_of_week",
+  "shift_preferences",
+  "call_preference",
+  "shift_lengths_hours",
+  "work_types",
+  "contract_types",
+  "minimum_hourly_rate",
+  "minimum_annual_salary",
+  "rate_visibility"
+]

AddedOct 21, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, and the description is consistent while adding real depth: it is a stateless guided intake that must ask only the returned next_question, carry known facts forward, preserve skipped fields, and avoid enumerating missing_fields. The explicit 'does not save or publish' and PII exclusion are exactly the constraints an agent needs beyond the annotations.

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 trigger condition and then packs operational rules into a few dense sentences; every clause carries a rule. The semicolon-chained middle sentence is heavy but not wasteful.

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?

Output schema exists, so return values need not be explained, and the description covers the conversational protocol, statelessness, and non-persistence for a complex 16-parameter intake. What remains thin is per-parameter guidance and error/edge behavior, but the essential call mechanics are present.

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?

With 50% schema coverage across 16 parameters, the schema does substantial work, and the description reinforces the skipped_optional_fields contract and constrains input to exclude identity/contact data. However, it adds no meaning for the bulk of domain parameters (state, area_query, work_types, radius_miles, rate fields), so the gap is only partly closed.

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+resource: structuring one's own work terms as a draft for RxRooster review, and clarifies it 'creates no service record.' The 'own work terms' framing implicitly separates it from a job-posting draft sibling, but no sibling is named explicitly.

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?

Opens with an explicit trigger ('Use when a CRNA, SRNA, or anesthesiologist wants to structure their own work terms'), giving audience and intent clearly. It lacks an explicit when-not clause or a named alternative, leaving the boundary with prepare_anesthesia_job_draft to be inferred.

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

All RxRooster 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?