Skip to main content
Glama

get_percentiles

Compute percentile metrics (latency or cost) for LLM calls. Optionally group by day, hour, or minute for time-series analysis.

Instructions

Get percentile metrics over calls (POST /v1/query/percentiles). metric = 'latency' (ms) or 'cost' (USD); either a single value for the whole range, or a time series with groupBy='day'/'hour'/'minute'. Example phrasing: "daily p95 latency trend for last week". Computed with the nearest-rank method via window functions (D1 SQLite has no percentile_cont).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoModel filter
metricNoMetric kind, default = 'latency'latency
endTimeNoRange end ISO timestamp
groupByNoTime-series bucketing (omit = one value for the whole range, 'day' = daily, 'hour' = hourly, 'minute' = per minute)
providerNoProvider filter
startTimeNoRange start ISO timestamp (UTC; omit = all time)
Behavior4/5

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

With no annotations, the description carries the full burden. It explains the computation method (nearest-rank via window functions) and notes implementation specifics (D1 SQLite limitation). It also clarifies output behavior (single value vs. time series). Some details about response format are missing, but the key behaviors are disclosed.

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?

Two concise sentences convey the core purpose, available options, and implementation detail. No wasted words; every sentence adds meaning.

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?

Given 6 optional parameters and no output schema, the description covers essential behavior (metric types, time grouping, computation). It lacks explicit mention of return structure, but the example phrasing and method hint at the output. Overall, it is sufficiently complete for an agent to understand the tool's function.

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%, but the description adds value by explaining the metric and groupBy semantics in natural language, including defaults and example. It goes beyond the schema by describing how to interpret groupBy (time bucketing) and provides a concrete usage example.

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 clearly states it retrieves percentile metrics over calls, specifies metric options (latency/cost) and time series capability with groupBy. It references the specific API endpoint and provides an example phrase, making the purpose distinct from sibling tools like query_calls or get_cost_summary.

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?

The description indicates when to use the tool (for percentile queries) and describes the groupBy options for time series. It does not explicitly state when not to use it or compare to alternatives, but the context is clear enough for an agent.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/argosvix/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server