Skip to main content
Glama
Sign In

fivebar

by ar.fiveb
OverviewDiscussionsAdmin

Get overview

get_overview
Read-onlyIdempotent

How every site of the user's is doing, or one group's, in one call: each site's pageviews, visits and visitors over a range beside the period before, with each change, the clearest movers first. The answer's caveats are the rules that apply to its figures, such as visitors never adding up across sites: read them before reporting any figure, and pass on those that change what it means. Use it first for any question about more than one site, rather than get_site_summary once a site. It reads the sites list_sites lists, never someone else's public site. The range is given as for get_site_summary, each site's in its own days, the 7 whole days to yesterday by default, and filters narrow every site alike, by any dimension but goal, entry and exit. sort: moved, the default, how clearly each site's visits moved, the change over the square root of both periods' visits, so a small site doubling and a large one moving a tenth both lead; visits, the busiest first; or domain. noise marks a site whose change in visits is too small to read into. change is null where a site has nothing to compare with, and no_change says why; counted says how a site's periods were counted, and basis what that does. totals add pageviews and visits alone. limit, 1 to 200 (50 by default), is how many sites are given, following how many more there are, and nothing_counted the sites with nothing in either period. For why one moved, explain_change; for what is new on it, whats_new.

Input Schema

NameRequiredDescriptionDefault
toNoWith from: the last day, as YYYY-MM-DD, not after today.
daysNoThe last this many days, ending today unless ending says yesterday.
fromNoWith to: the first day, as YYYY-MM-DD.
sortNoThe order of the sites, moved by default.
groupNoOnly this group's sites, by its name as list_sites gives it, ignoring case; None for the first. Left out, every site of the user's.
limitNoHow many sites, 50 by default.
rangeNoA preset, as get_site_summary's range says what each covers.
endingNoWith days: the last day, today by default.
filtersNoEach narrows every figure to what has exactly that value, case and all, so google is not Google; all must hold.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / range / enum
      Previous value: -[
-  "today",
-  "yesterday",
-  "this-week",
-  "this-week-sun",
-  "last-7-days",
-  "last-week",
-  "last-week-sun",
-  "last-14-days",
-  "this-month",
-  "last-30-days",
-  "last-month",
-  "all-time"
-]New value: +[
+  "today",
+  "yesterday",
+  "this-week",
+  "this-week-fri",
+  "this-week-sat",
+  "this-week-sun",
+  "last-7-days",
+  "last-week",
+  "last-week-fri",
+  "last-week-sat",
+  "last-week-sun",
+  "last-14-days",
+  "this-month",
+  "last-30-days",
+  "last-month",
+  "all-time"
+]
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses key behavioral caveats: visitors do not add up across sites, change is null when there is nothing to compare with, no_change explains why, counted/basis explain period counting, totals add pageviews and visits only, and noise flags unreliable movement.

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?

The description is front-loaded with purpose and caveats, and most clauses earn their place. It is dense and occasionally run-on, but the length is largely justified by the tool's nine parameters and many output-field semantics.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description explains the important returned fields and edge cases: change/no_change, counted/basis, totals, noise, limit and nothing_counted. Combined with the annotations, an agent has enough context to call and interpret it correctly.

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

Parameters5/5

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

Schema coverage is complete, but the description adds substantial meaning beyond it: sort=moved is defined with its square-root formula, limit follows how many more sites exist, filters narrow every site alike, and default range behavior is clarified as the 7 whole days to yesterday.

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?

The description states a specific verb and resource: aggregate pageviews, visits and visitors across every site or one group, with before-period comparison and sorted movers. It also explicitly distinguishes itself from get_site_summary for multi-site questions and from explain_change/whats_new for follow-ups.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit routing guidance: use this first for any question about more than one site, rather than get_site_summary once a site. It also names explain_change for why one moved and whats_new for what is new, plus notes filters cannot use goal, entry or exit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All fivebar toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources