Skip to main content
Glama

get_analytics

Read-onlyIdempotent

Retrieve merge-queue analytics for a date range, including time in queue, merged PRs, and blocked reasons; optionally return daily rows.

Instructions

Merge-queue analytics for a date range: time in queue, PRs merged, blocked reasons. Returns a summary; daily rows on request.

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_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoYYYY-MM-DD (UTC)
orgNoGitHub org. Optional if repo is 'org/name'.
repoNoGitHub repo name or 'org/name'.
startNoYYYY-MM-DD (UTC)
timezoneNoe.g. Europe/Bucharest
include_dailyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely new behavioral context: the default return is a summary, and per-day rows only appear when requested. It does not mention auth requirements or how the timezone affects bucketing, which would have raised it further.

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 short sentences, front-loaded with the resource and metrics, then the return-shape caveat. Every clause carries information; there is no filler or redundant restatement of the name.

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 six parameters, no required fields, and no output schema, the description does the important work of sketching the return shape (summary vs daily rows). It leaves the org/repo interaction and default timezone behavior unexplained, which are the main remaining gaps for a reporting tool.

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 coverage is 83%, so the schema already documents start, end, org, repo and timezone formats. The description compensates for the one weak spot by explaining that include_daily yields daily rows rather than the default summary. It adds nothing about the org/repo resolution rule or timezone semantics beyond what the schema states.

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 names a specific verb-resource pair ('Merge-queue analytics') and enumerates the concrete metrics produced ('time in queue, PRs merged, blocked reasons'), so an agent knows exactly what it gets back. It does not distinguish itself from the sibling get_queue_stats, which an agent could plausibly confuse it with.

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?

There is no statement of when to use this versus get_queue_stats, get_pr_status, or list_queued_prs, nor any prerequisite or exclusion. The only implicit guidance is 'for a date range', which the required-optional schema already implies. The agent is left to infer selection from the metric list alone.

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