Skip to main content
Glama

Explain one route, screen or dependency

get_endpoint_summary
Read-only

Everything about one row of the Performance page, to answer 'why is this slow?': count, error rate, p50 to p99 and the change against the window before; where the time goes inside each request (database, HTTP and model calls, and the backend routes a screen waited on); what the slowest 10% have that the rest don't (release, status, device…) and which inner spans grow most in them; who calls a dependency; per-release numbers; sample traces (slowest, typical, fastest, failed: open them with get_trace); and the open issues on that route. op is like http.server, ui.load, ui.pageload, http.client, db, gen_ai, task; route is the route, screen, page, host or table as get_performance_overview lists it.

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": {
      "op": "<op>",
      "route": "<route>"
    },
    "name": "get_endpoint_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
opYesThe row's op, like http.server
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.
routeYesThe row's route, screen, page, host or table
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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds real behavioral context by enumerating the returned analysis (percentiles, change vs. prior window, span time breakdown, slowest-10% differentials, per-release numbers, sample traces, open issues). It does not mention response size, sampling, or whether the 'slowest 10%' comparison needs sufficient volume, which is the remaining 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?

Front-loaded with the purpose and the user question, then a dense enumeration of contents that all maps to real returned data. It is a single long run-on sentence-chain, so it is harder to scan than it needs to be, but little of it is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the full burden of explaining returns, and it does so exhaustively for a 9-parameter read tool, including the cross-tool handoff to get_trace for trace detail. Defaults for time range and environment are handled in the schema, so nothing an agent needs to call it correctly is missing.

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%, so the baseline is 3, but the description adds genuine meaning: it lists concrete op values (http.server, ui.load, ui.pageload, http.client, db, gen_ai, task) that the schema only gestures at with one example, and clarifies that route can be a screen, page, host or table. It says nothing extra about source, release, service, or environment, which the schema already documents.

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?

States a concrete verb+resource: 'Everything about one row of the Performance page', scoped to a single op/route pair, and frames the question it answers ('why is this slow?'). It also distinguishes itself from get_performance_overview by defining route/op as that tool lists them, so an agent can pick the right one 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?

Gives a clear triggering question ('why is this slow?') and an explicit handoff for a related step: sample traces should be opened with get_trace. It does not state when NOT to use it (e.g. fleet-wide comparisons belong in get_performance_overview), so it stops short of full alternative routing.

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