Vitalli

vora_set_traffic_light

DestructiveIdempotent

Sets the signed-in user's own traffic-light levels for one numeric biomarker and replaces existing ones. The limits are the user's own; Vora suggests and rates nothing. 2 to 5 levels: n-1 limits in ascending order for n levels, plus the direction. Colors follow from count and direction (lower_better: green, yellow, orange, red, violet from low to high values; higher_better: reversed). Scale values such as the Bristol chart have no levels.

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": {
      "slug": "<slug>",
      "direction": "<direction>",
      "bounds": "<bounds>"
    },
    "name": "vora_set_traffic_light"
  }
}

Input Schema

Name	Required	Description
`slug`	Yes	Biomarker slug, e.g. 'gki'
`bounds`	Yes	Limits in ascending order, e.g. [1, 2, 3] for green <1, yellow <2, orange <3, red ≥3
`labels`	No	Optional own label per level, lowest values first; null keeps the color name
`direction`	Yes	Whether a lower or a higher value is better, as stated by the user

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true; the description corroborates this with 'replaces existing ones' and adds substantive behavioral rules — 2 to 5 levels, n-1 limits, and how colors are derived from count and direction. It does not cover error behavior (e.g. non-numeric biomarkers) or permission/auth requirements, leaving a modest 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?

Three sentences, front-loaded with the action and replacement semantics, followed by the structural rules and the scale-chart exclusion. Dense but every sentence earns its place; the color enumeration for both directions is slightly verbose but operationally useful.

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?

For a 4-parameter destructive mutation with no output schema, the description covers the counting rule, ordering, direction, color derivation, and the non-numeric exclusion. Missing items are minor: label behavior and what happens if the biomarker is unknown or the slug invalid.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, establishing a baseline of 3, and the description adds genuine cross-parameter meaning: the n-1-limits-for-n-levels relationship between 'bounds' and level count, the required ascending order, and how 'direction' determines color ordering. It says nothing about the optional 'labels' parameter, which is the one gap.

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 opens with a specific verb+resource+scope: setting the signed-in user's own traffic-light levels for one numeric biomarker, and names the replacement semantics. This clearly separates it from vora_get_traffic_lights and vora_delete_traffic_light without the agent needing to open schemas.

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?

It provides a concrete exclusion: 'Scale values such as the Bristol chart have no levels', which steers the agent away from using this for scale-based biomarkers (e.g. vora_add_bristol). It does not explicitly name a read-before-write alternative or state prerequisites, so it is clear but not fully routing.

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

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