Skip to main content
Glama
fridzema

clockwork-mcp

by fridzema

analyze_route_performance

Analyze HTTP route performance using percentile statistics. Filter by URI, time period, or request count to identify slow routes.

Instructions

Analyze route performance with percentile statistics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestIdNoSpecific request ID (highest priority)
countNoNumber of recent HTTP requests to analyze
sinceNoTime duration to look back (e.g., "30m", "1h", "2d", "1w")
allNoAnalyze all available requests (max 100)
uriNoFilter by URI pattern (substring match)
groupByNoHow to group routesuri
minSamplesNoMinimum samples required for a route
Behavior1/5

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

No annotations provided; description fails to disclose any behavioral traits like side effects, permissions, or rate limits.

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?

Single sentence is concise with no wasted words, though it lacks depth.

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

Completeness1/5

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

With 7 parameters, no output schema, and no annotations, the description is far too minimal to provide adequate context for effective use.

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 documentation covers all 7 parameters, so description adds no extra meaning beyond what's already in the schema.

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?

Description clearly states 'Analyze route performance' with specific mention of 'percentile statistics', distinguishing it from siblings like get_performance_summary.

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?

No guidance on when to use this tool vs alternatives such as get_performance_summary or get_http_requests.

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/fridzema/clockwork-mcp'

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