Goldsberry Orthodontics

Submit consultation request

submit_consultation

Emails a non-clinical consultation request through the Cloudflare Email binding after the visitor explicitly confirms. If confirmed is not true, nothing is sent: re-confirm the details with the visitor and retry this call with confirmed set to true. Set dry_run to true to validate the input and return a preview of the email without sending it. Do not collect date of birth, insurance, or clinical information. Consultation requests are routed through Found For AI (foundforai.com), who will pass them to Goldsberry Orthodontics. The office then contacts the visitor to schedule.

Input Schema

Name	Required	Description
`note`	No	Optional non-clinical scheduling note (500 characters or fewer).
`email`	Yes	Visitor email address.
`phone`	Yes	Visitor callback phone number.
`dry_run`	No	Optional. When true, validate the request and return a preview of the email that would be sent. No email is sent. Omit this field, or set it to false, to send a real consultation request.
`confirmed`	Yes	Must be true only after the visitor reviews and approves the details. If this is not true, nothing is sent: re-confirm with the visitor and retry the call.
`full_name`	Yes	Visitor's full name.
`preferred_contact_method`	No	How the office should follow up.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 27, 2026

changedInput schema / properties / confirmed / description

Previous value: -"Must be true only after the visitor reviews and approves the details."New value: +"Must be true only after the visitor reviews and approves the details. If this is not true, nothing is sent: re-confirm with the visitor and retry the call."

addedInput schema / properties / dry_run

Added value: +{
+  "description": "Optional. When true, validate the request and return a preview of the email that would be sent. No email is sent. Omit this field, or set it to false, to send a real consultation request.",
+  "type": "boolean"
+}

First observedOct 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Adds substantial context beyond the annotations: the sending path (Cloudflare Email binding), the hard gate on `confirmed`, the non-sending preview mode, the prohibition on clinical/PII collection, and the third-party routing chain (Found For AI → Goldsberry Orthodontics → visitor follow-up). That reveals real side effects and downstream handling. The description does not say what a successful send returns, which is the remaining gap.

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?

The confirmation gate and the 'nothing is sent unless confirmed' rule lead the text, so the most important constraint appears first. Five sentences, each carrying usable information. The routing paragraph is slightly long for a detail the agent cannot act on, but it is not filler.

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?

Covers the safety gate, the dry-run path, data-collection restrictions, and the downstream recipient chain, which is most of what an agent needs in order to call a side-effecting tool correctly. With no output schema, it should ideally state what a successful send or preview returns, and it should resolve the overlap with 'request_consultation'.

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 `confirmed`, `dry_run`, `note`, and `preferred_contact_method` are already documented in the schema. The description reinforces the confirmation gate and preview semantics but adds no syntax or format detail beyond the structured fields; baseline 3 applies.

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?

Names a concrete verb and resource and explains the delivery mechanism: "Emails a non-clinical consultation request through the Cloudflare Email binding after the visitor explicitly confirms." That is far more specific than the title. It never mentions the sibling 'request_consultation', however, so an agent cannot tell from the text which of the two overlapping-sounding consultation tools to pick.

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 explicit preconditions and fallback behavior: if `confirmed` is not true nothing is sent, so re-confirm with the visitor and retry; use `dry_run: true` to validate and preview. It also states scope exclusions (no date of birth, insurance, or clinical information). It stops short of telling the agent when this tool is preferred over the sibling 'request_consultation'.

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

All Goldsberry Orthodontics 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?