Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Events by day

usage_events_by_day
Read-onlyIdempotent

Page views plus custom events for each day of this month.

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": {
      "siteId": "<siteId>"
    },
    "name": "usage_events_by_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real scope context — that results are daily buckets limited to the current month — but says nothing about timezone handling, zero/empty days, or result size, which matter for a time-series read.

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?

A single front-loaded sentence with no filler; the resource and time scope come first. It is a fragment lacking an explicit verb, but nothing is wasted.

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 simple one-parameter read tool with no output schema and strong annotations, the description covers what is returned and the time window, which is the core need. It leaves out the siteId requirement and any indication of response shape or empty-day behavior, so it is adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required parameter, siteId, and schema description coverage is 0%, so the description carries the full burden of explaining it — yet siteId is never mentioned, nor is whether the tool is implicitly scoped to a site. The only compensation is the 'this month' range constraint, which is not a parameter.

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 the returned resource (page views plus custom events) and its granularity and time scope (each day of this month), which is more specific than the bare title 'Events by day'. It stops short of distinguishing itself from sibling analytics series tools such as analytics_getEventDataDateSeries, but an agent can still tell what data comes back.

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 guidance on when to choose this over the many daily/series siblings, no exclusion conditions, and no stated prerequisites. The only hint is the implicit 'this month' scope, which is a boundary rather than usage 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