TuneWorks

Send Share Build

send_share_build

Emails selected TuneWorks vehicle, setup, and session details to up to three recipients. Explicit user confirmation is required.

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": {
      "vehicleId": "<vehicleId>",
      "recipients": "<recipients>",
      "confirmed": "<confirmed>"
    },
    "name": "send_share_build"
  }
}

Input Schema

Name	Required	Description
`message`	No	Optional message to include in the Share Build email.
`setupIds`	No	Optional TuneWorks setup IDs to include.
`confirmed`	Yes	True indicates that the user explicitly confirmed the recipient list and selected build details.
`vehicleId`	Yes	TuneWorks vehicle ID selected for Share Build.
`recipients`	Yes	Recipient email addresses. Share Build supports up to 3 recipients.
`sessionIds`	No	Optional TuneWorks session IDs to include.

Output Schema

Name	Required	Description
`id`	No
`tool`	Yes	TuneWorks MCP tool name that produced this result.
`user`	No
`status`	Yes	Stable result status such as ok, created, updated, sent, auth_required, or confirmation_required.
`message`	No
`outcome`	No	Optional domain outcome for an otherwise successful read.
`actionType`	No
`previewTool`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 24, 2026

addedOutput schema / properties / outcome

Added value: +{
+  "description": "Optional domain outcome for an otherwise successful read.",
+  "enum": [
+    "no_vehicles",
+    "vehicle_not_found",
+    "vehicle_selection_required",
+    "no_data"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / status / description

Previous value: -"Result status such as ok, created, updated, sent, auth_required, or confirmation_required."New value: +"Stable result status such as ok, created, updated, sent, auth_required, or confirmation_required."

First observedOct 18, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare that this is a non-read-only, open-world, non-destructive action. The description adds useful behavioral context: it sends an actual email externally, supports up to three recipients, and requires explicit user confirmation.

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 two focused sentences with no wasted words. The action is front-loaded, and the confirmation requirement is stated immediately after the core behavior.

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

Completeness3/5

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

The presence of an output schema and annotations reduces the burden on the description, and the description covers the core action, recipient limit, and confirmation requirement. However, it omits routing guidance to closely related siblings such as preview_share_build and get_share_build_options, which would make the context more complete for an agent.

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 all six parameters are already documented in the input schema. The description reinforces recipient limits and the vehicle/setup/session content being sent, but does not add syntax or meaning beyond the schema.

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?

The description states a specific verb and resource: it emails selected TuneWorks vehicle, setup, and session details to recipients. It is clear what the tool does, but it does not explicitly distinguish itself from related siblings such as preview_share_build or get_share_build_options.

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

Usage Guidelines3/5

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

The description states a key precondition, explicit user confirmation, which helps determine when the tool may be invoked. However, it gives no guidance on when to use this send tool versus preview_share_build or get_share_build_options, leaving that alternative routing implicit.

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

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