Skip to main content
Glama

Dashboard and report metrics

metrics_summary
Read-onlyIdempotent

Aggregate numbers, not individual records: the current dashboard snapshot, a named day/week/month's totals, or a summary over an arbitrary date range. Note: the 'range' period is restricted by cpass to admin-tier roles, so it may 403 for an ordinary agent's connection independent of what was granted here. Read only.

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": {
      "period": "<period>"
    },
    "name": "metrics_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoRequired for period="daily". ISO date, e.g. "2026-10-04"
yearNoRequired for period="monthly"
monthNoRequired for period="monthly". 1-12
periodYesWhich report to fetch — see the per-period fields below for what each needs
endDateNoRequired for period="range". ISO date, inclusive
startDateNoRequired for period="range". ISO date, inclusive
weekStartDateNoRequired for period="weekly". ISO date for the week's first day

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is lower and the useful addition here is the permission disclosure: 'range' is admin-tier and may return 403 regardless of grants on this tool. That is non-obvious operational context an agent cannot get from annotations or schema. The trailing 'Read only' merely restates readOnlyHint, and the response shape is never characterized.

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?

Two sentences that front-load the core distinction and then append the permission caveat in the right place. Only 'Read only.' is wasted, since it duplicates the readOnlyHint annotation.

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

Completeness3/5

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

For a 7-parameter tool with five enum values and conditional required fields, the description covers selection logic and the access caveat well. With no output schema, however, nothing tells the agent what numbers or dimensions come back from a metrics summary, which is a real gap for a reporting tool.

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 schema documents each conditional field, giving a baseline of 3. The description adds meaning beyond that by mapping periods to their concrete meanings (snapshot vs. named period vs. arbitrary range) and by flagging the admin restriction attached to the 'range' value specifically.

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 specific verb and resource ('Aggregate numbers, not individual records') and enumerates the four aggregation modes (current snapshot, named day/week/month, arbitrary range). The 'not individual records' framing immediately separates it from record-level siblings such as call_list or contact_list.

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?

The description makes clear which reporting shape to pick and warns that the 'range' period may 403 for non-admin connections, which is genuine when-to-use guidance. It does not, however, explicitly name a sibling alternative for record-level needs, leaving that routing to inference.

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.