Skip to main content
Glama

messages_histogram

Read-onlyIdempotent

Count log messages per hour, day or week, to see when errors started, spiked or stopped. Empty buckets are included with a count of 0. Use messages_count for a single total.

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": {
      "logId": "<logId>"
    },
    "name": "messages_histogram"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoSearch to this date (default now).
fromNoSearch from this date (default is the start of the organization's retention period).
logIdYesThe ID (Guid) of the log.
queryNoFull-text or Lucene query, e.g. statusCode:500 && url:*\/api\/*. Searchable fields are listed in the server instructions.
hiddenNoInclude hidden messages (default false).
intervalNoBucket size: hour|day|week. Default is chosen from the date range (hour up to 2 days, day up to 100 days, otherwise week). At most 200 buckets are returned.
severityNoOptional severity filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / from / description
      Previous value: -"Search from this date (default 30 days ago)."New value: +"Search from this date (default is the start of the organization's retention period)."
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this a safe read-only, idempotent, non-destructive and closed-world operation, so safety is covered. The description adds meaningful aggregation behavior beyond that: empty buckets are returned with a count of 0, which prevents an agent from misreading gaps as missing data. It does not describe output shape or bucket-cap behavior (the cap lives in the schema), leaving a modest gap.

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?

Three short sentences, front-loaded with purpose, then the empty-bucket behavior, then the sibling routing. No filler or repetition; every sentence carries information an agent would otherwise have to infer.

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 aggregation tool with no output schema, the description conveys the unit of the result (counts per bucket) and the zero-filled behavior, which is the main ambiguity. It omits the bucket cap and return field naming, but those are either in the schema or minor for correct invocation.

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 every parameter already has inline documentation including interval semantics and defaults. The description only refers generally to hour/day/week bucketing and adds no syntax, constraints, or defaults beyond the schema, so the baseline of 3 applies.

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 ('Count log messages') plus the bucketing dimension (hour, day, week) and the diagnostic purpose (see when errors started, spiked or stopped). It names the sibling it is not, messages_count, so an agent can separate aggregation from a single total without reading either schema.

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 a clear context ('to see when errors started, spiked or stopped') and explicitly routes the single-total case to messages_count. It does not state exclusions such as raw message retrieval or when a different grouping is preferable, so it stops short of full when/when-not 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