Skip to main content
Glama

Tally by Outpost

Peak hours

get_peak_hours
Read-onlyIdempotent

Visits, sales and revenue by weekday and hour in the site's time zone, and the busiest three hours when the data is enough to say.

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_peak_hours"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoA custom range's last day (YYYY-MM-DD), with from.
fromNoA custom range's first day (YYYY-MM-DD), with to. Up to 366 days, not past today.
siteNoThe site's id. Optional: the API key's site is the one read.
periodNoA preset period, in the site's time zone. Leave out for the tool's default, or give from and to instead.
filtersNoVisits that match every filter (AND). Each dimension at most once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds two genuine behavioral facts beyond that: results are bucketed in the site's time zone, and the busiest-three-hours field is conditional on sufficient data. It says nothing about granularity limits, empty-bucket handling, or the shape of the response, which matters since there is no output schema.

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?

A single front-loaded sentence with no filler; the primary output is stated first and the conditional caveat trails it. Every clause carries information.

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 analytics tool with a fully documented schema and no output schema, the description covers the metrics returned, the breakdown axes, the time-zone basis, and the conditional extra output. What remains unstated — response shape, how sparse data is rendered — is modest given the rich annotations and complete parameter documentation.

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 coverage is 100%, with each of the five parameters (to, from, site, period, filters) fully described in the schema, so the schema carries the parameter burden. The description adds no syntax, default-value, or interaction detail (e.g., from/to vs period precedence) beyond what the schema already states. Baseline 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?

Names the concrete metrics (visits, sales, revenue) and the exact breakdown axes (weekday and hour), plus the derived output (busiest three hours). This is specific enough to separate it from get_breakdown or get_overview, though it never explicitly contrasts with those siblings.

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 when-to-use guidance, no exclusions, and no pointer to an alternative such as get_breakdown for ad-hoc dimension slicing. The only usage-adjacent statement is the data-sufficiency caveat ('when the data is enough to say'), which constrains the output rather than telling the agent when to pick this tool.

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