ReactionMetric MCP

summarize_reaction_trials

Calculate a transparent median of five user-supplied valid browser-observed reaction times in milliseconds; no calibration or population percentile claims.

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": {
      "trials_ms": "<trials_ms>"
    },
    "name": "summarize_reaction_trials"
  }
}

Input Schema

Name	Required	Description	Default
`trials_ms`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the algorithm intent ('transparent median', i.e., plain median, not a trimmed/calibrated estimate) and a negative scope (no percentile claims), but says nothing about output format or error behavior for invalid input.

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?

A single front-loaded sentence with the verb and resource first, then the scope caveat. Every clause earns its place with no filler.

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?

For a small computation tool with no output schema and no annotations, the description is adequate on input and scope but omits what is returned (the median value) and how invalid or out-of-range input is handled. Enough to call it, but not fully complete.

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 description coverage is 0%, so the description must compensate for the single parameter, and it does: it conveys count (five), unit (milliseconds), and qualifying semantics (user-supplied, valid, browser-observed). This meaningfully enriches the bare 'trials_ms' array.

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 (Calculate) and resource (median of five user-supplied reaction times in ms), so the operation is unambiguous. It does not, however, reference the sibling find_reaction_test or otherwise differentiate the two, keeping it below a 5.

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?

Usage is only implied by the computation itself; there is no explicit when-to-use, no named alternative, and no prerequisites. The 'no calibration or population percentile claims' clause hints at an exclusion, but it reads as a scope disclaimer rather than routing guidance.

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

All ReactionMetric MCP 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?