Privi Agent Survival & Premium

Latency statistics

privi_latency_percentiles

Read-only

Report min, mean, p50, p90, p95, p99 and max from a supplied latency sample.

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": {
      "milliseconds": "<milliseconds>"
    },
    "name": "privi_latency_percentiles"
  }
}

Input Schema

Name	Required	Description	Default
`milliseconds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

B3.3/5.0

Behavior4/5

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

The annotations already establish that this is read-only and closed-world. Beyond that, the description usefully discloses the exact metrics computed, which is meaningful behavioral information, though it omits handling of empty samples, invalid values, and output ordering.

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 definition is a single front-loaded sentence with no filler. It states the operation and the exact reported metrics efficiently.

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 simple read-only percentile tool with no output schema, the description does list the returned statistics. However, the undocumented input array and missing edge-case behavior leave meaningful gaps for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the single required parameter is undocumented structurally. The description only says "supplied latency sample" and does not explain that the parameter is an array of millisecond values, whether elements must be numbers, or any format expectations.

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 uses the specific verb "Report" and names exactly which statistics (min, mean, p50, p90, p95, p99, max) are computed from a latency sample. That is clear enough to distinguish this as a percentile/statistics helper, though it does not explicitly contrast with the related latency SLO sibling.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no exclusions, and no named alternatives. The only contextual cue is "from a supplied latency sample," which implies usage but does not tell an agent when to choose this over privi_pro_latency_slo or other siblings.

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

All Privi Agent Survival & Premium tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.