Skip to main content
Glama

Get Analytics

get_analytics

Return a compact analytics summary for this workspace over the last days days (default 30): conversation counts + resolution rate, message volume + AI share, plus a live snapshot of today (UTC). resolved, resolutionRatePct and avgResolutionHours exclude conversations closed by auto-resolve; autoResolved counts those separately and resolvedIncludingAuto is the total including them.

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
daysNoLook-back window in days for the conversation/message stats (default 30).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work by defining how resolution metrics exclude auto-resolved conversations. It also clarifies that `autoResolved` and `resolvedIncludingAuto` are reported separately and that the today snapshot is live and UTC-based. It does not mention permissions, rate limits, or response formatting, but the metric semantics are unusually well disclosed.

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?

The description is two sentences, front-loaded with the tool's purpose before moving into metric definitions. It is dense but each clause carries useful information about what is returned. The second sentence is somewhat packed, yet it remains focused and avoids filler.

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?

For a read-oriented analytics tool with one optional parameter and no output schema, the description is largely complete. It explains the returned metric families and important resolution-rate semantics, including auto-resolve exclusions. It could say more about permissions or the exact response structure, but the essential invocation and interpretation context is present.

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 the `days` parameter is already documented as a look-back window with a default of 30. The description restates the default and clarifies that the window applies to conversation/message stats while the today snapshot is live, which adds marginal context. Given the schema already does the heavy lifting, a baseline score of 3 is appropriate.

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 states a specific verb and resource: returning a compact analytics summary for this workspace over a configurable day window. It enumerates the metric families covered, including conversation counts, resolution rate, message volume, AI share, and a live today snapshot. The scope is clear, though it does not explicitly distinguish itself from sibling tools.

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?

The description implies an analytics/reporting use case but gives no explicit guidance on when to choose this tool versus alternatives. There are no exclusions, prerequisites, or routing conditions. An agent can infer it is for workspace-level analytics, but that is the extent of the guidance.

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