Skip to main content
Glama

Estatísticas de atividade

activity_stats
Read-only

Totais do histórico de atividade por tipo e por ação no período (mesmos itens de activity_history). Use para "quantos números caíram este mês" ou "quantos incidentes tivemos".

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": {
      "de": "<de>",
      "ate": "<ate>"
    },
    "name": "activity_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
deYesInício do período. Data ISO (AAAA-MM-DD ou com hora e fuso) ou epoch em segundos.
ateYesFim do período. Data ISO (AAAA-MM-DD ou com hora e fuso) ou epoch em segundos.

Output Schema

NameRequiredDescriptionDefault
deNoISO 8601 com o fuso de Brasília (-03:00).
ateNoISO 8601 com o fuso de Brasília (-03:00).
totalNo
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds the meaningful behavioral fact that results are grouped by type and by action over a bounded period, and that it draws on the same dataset as activity_history. Return shape is covered by the output schema, so no penalty for omitting it.

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 with zero filler: the aggregation scope is front-loaded, followed by the intent examples. Every clause earns its place and nothing needs to be scanned twice.

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-only two-parameter aggregation tool with full schema coverage and an output schema, the description supplies what's needed to call it correctly: what is aggregated, the grouping keys, and the time window. The only gap is the missing explicit routing rule to activity_history for raw rows, which would have made the pair fully self-navigating.

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% and both parameters document accepted formats (ISO date or epoch seconds) in detail, so the schema carries the load. The description only contributes the notion of a bounded period ('no período'), adding no format or boundary semantics 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?

States a specific resource and aggregation: totals of activity history broken down by type and by action within a period. It ties itself to the sibling activity_history ('mesmos itens de activity_history'), which lets an agent infer this is the aggregate view rather than the raw list. It stops short of an explicit contrast statement, but the verb+resource+grouping is unambiguous.

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?

Gives concrete natural-language question patterns ('quantos números caíram este mês', 'quantos incidentes tivemos'), which maps well to real agent intents and signals this is the counting/aggregation tool. It does not explicitly say to use activity_history when raw per-event rows are needed, so the exclusion is only implied by the parenthetical.

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