Skip to main content
Glama

Tally by Outpost

Realtime

get_realtime
Read-onlyIdempotent

Who is on the site in the last five minutes (page, place, source, device) and the sales of the last hour.

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

Input Schema

NameRequiredDescriptionDefault
siteNoThe site's id. Optional: the API key's site is the one read.
limitNoRows at most (default 100).
filtersNoVisits that match every filter (AND). Each dimension at most once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so safety is covered. The description adds the two time windows (five minutes, one hour) and the content dimensions, which is useful behavioral context, but it omits any note on return format or pagination.

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 zero filler. It efficiently conveys the core output, though it could be slightly expanded to include a hint about filtering or defaults without losing conciseness.

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 three-parameter tool with a nested filter object and no output schema, the description gives a reasonable summary of returned content (visitors and sales). However, it does not clarify the shape of the response—whether it is a list of visitors with aggregated sales, a summary, etc.—which is important given the lack of an output schema.

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 schema fully explains the three parameters and the nested filter dimensions. The description adds no parameter-level meaning beyond what the schema already provides, making the baseline score of 3 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+resource: it returns current site visitors (last five minutes) and sales (last hour), with the dimensions page, place, source, and device. This is clearly distinct from historical or breakdown siblings, though no sibling is named for contrast.

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 explicit when-to-use or when-not-to-use guidance, and no alternative tool is mentioned. The time windows imply a real-time monitoring use case, but the description offers no routing advice.

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