Skip to main content
Glama

Performance overview

get_performance_overview
Read-only

How fast the app is right now, backend and frontend: backend requests per minute, p95 and error rate against the window before; screen and page load times; then the routes that take the most total time, the slowest screens and pages, and the slowest dependencies (HTTP hosts, database tables). Start here, then open one with get_endpoint_summary.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_performance_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoAn ISO time, or how long ago (default now)
fromNoAn ISO time, or how long ago: 30m, 24h, 7d
rangeNoWindow: 1h, 24h, 7d, 14d, 30d or 90d (default 24h). Ignored when from is given.
sourceNobackend (servers), frontend (app and web), or all (default)
releaseNoOnly this release: 2.0.77+185, 2.0.77 (every build) or package@2.0.77+185
serviceNoOnly this service, like house-ai-api or the app's bundle id
environmentNoLike production. Default: production when the app has it, else its busiest non-development one. 'all' for every environment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / release / description
      Previous value: -"Only this release (service version)"New value: +"Only this release: 2.0.77+185, 2.0.77 (every build) or package@2.0.77+185"
  2. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so the safety profile is fully covered. What the description adds is the comparison baseline ('against the window before'), which is genuine context an agent cannot get from annotations or schema. It says nothing about latency, cost, rate limits, or truncation of the 'top routes' lists, so the added value is real but modest.

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?

Front-loaded with the core question ('How fast the app is right now'), then a tight semicolon-separated enumeration of returned sections, then the routing sentence. No filler, no restatement of the tool name, and the actionable ordering instruction is placed last where it lands.

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?

With seven optional parameters, no output schema, and an aggregation tool, the description does well to enumerate what sections come back and what the comparison baseline is. Remaining gaps are minor: it does not state the return shape (object vs. report), granularity, or whether empty backend/frontend sides yield nulls; the 100% schema coverage offsets the parameter side.

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% and every one of the seven parameters is documented in-schema, including enum values and defaults, so the baseline is 3. The description only reinforces the notion of a comparison window and does not explain the from/to vs. range precedence or the release/service scoping syntax beyond what the schema states.

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?

Names a specific verb-and-resource pair ('How fast the app is right now, backend and frontend') and enumerates the exact payload: requests per minute, p95, error rate vs. the prior window, load times, slowest routes/screens, slowest dependencies. The closing line routes the agent to the sibling that drills in, so it is distinguishable from get_endpoint_summary without opening a schema.

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?

'Start here, then open one with get_endpoint_summary' gives an explicit entry-point role and an explicit next-step alternative, which is strong ordering guidance. It stops short of stating when *not* to use this tool (for example, when targeting a single known route or a non-performance question), so it is clear context rather than full when/when-not coverage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources