Skip to main content
Glama

Get error trends

runheed_get_trends
Read-only

Returns error statistics for the last 24 hours, 7 days or 30 days: total, new and resolved counts, the most frequent errors and the hourly error rate.

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": "runheed_get_trends"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNoTime period to analyze24h
projectIdNoFilter by project id or slug (e.g. shop-api)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / projectId / description
      Previous value: -"Filter by project ID"New value: +"Filter by project id or slug (e.g. shop-api)"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the description doesn't need to restate safety. It does add real value by disclosing the shape of the result — the specific aggregates and the hourly rate series — which matters because no output schema exists. It does not mention aggregation granularity caveats, empty-window behavior, or volume of data returned, keeping it below a 5.

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?

A single sentence, front-loaded with the verb and resource, then the return contents. Every clause carries information and nothing is padded or repeated.

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 no output schema, the description has to carry the return contract, and it does so well for a two-parameter read-only aggregation. The main remaining gap is scope: it never says whether the statistics cover the whole workspace or are narrowed by projectId, and 'hourly error rate' is left undefined. These are minor for a low-complexity tool but keep it from a 5.

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%, so both parameters are already documented, and the description merely echoes the enum values ('24 hours, 7 days or 30 days') without adding interpretation. The projectId filter — arguably the more consequential scoping parameter — is never mentioned in the description, so no meaning is added beyond the schema. Baseline 3 applies.

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 gives a specific verb ('Returns') plus the resource ('error statistics') and enumerates the payload: totals, new/resolved counts, top errors, and hourly rate. That is far more informative than the title alone. It stops short of explicitly contrasting itself with siblings like get_project_health or get_recent, which also sound retrospective, so an agent must infer the boundary.

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

Usage Guidelines3/5

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

Usage is only implied: the mention of fixed windows (24h/7d/30d) and trend metrics signals 'aggregated time-series analysis' versus a single-error lookup. There is no explicit statement of when to prefer this over runheed_get_project_health or runheed_get_recent, and no exclusions or prerequisites are given.

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.