Skip to main content
Glama
Sign In

fivebar

by ar.fiveb
OverviewDiscussionsAdmin

What is new

whats_new
Read-onlyIdempotent

What changed on a site between a range and the period before, found by fixed rules and given most pressing first. The answer's caveats are the rules that apply to its figures, such as what new means: read them before reporting any figure, and pass on those that change what it means. It looks for server errors, goals no longer reached, pages newly answering with errors or an error rate that rose, speed rated worse, pages whose loads turned slow, goals reached far less, sources, countries and pages that fell away or took off, and sources, referrers, campaigns, pages and goals that are new; with revenue, its first, sources newly bringing it and channels whose revenue per visit moved. Use it for what is new, what is wrong or what to look at. Each finding has its kind as finding, what it says, its figures, and the filter or dashboard link to see it, at most 5 a kind, unlisted counting the rest. Only what clears its kind's rule, as rules gives each with its floor, is a finding: a new value can be a few visits; checked lists the kinds looked for that found nothing, and skipped those that could not be looked for, and why. New means counted in the range and not in new_means, the days before it back to 28 before the period compared with. Name the site and range as for get_site_summary, but for all time, the 7 whole days to yesterday by default; it takes no filters.

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.
rangeNoA preset, as get_site_summary's range says what each covers.
domainYesA domain from list_sites, or any public site's.
endingNoWith days: the last day, today by default.

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"
-]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"
+]
  2. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Despite read-only annotations, the description adds substantial behavioral detail: fixed rules, caveats that must be read before reporting figures, result caps per finding kind, checked/skipped lists, and the definition of 'new' relative to the preceding comparison period. This is far more context than the annotations alone provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense, run-on, and difficult to parse. Many clauses are packed into long sentences, and key behavioral details are buried rather than structured. It front-loads the purpose but then becomes verbose and hard to scan.

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?

With no output schema, the description carries the burden of explaining return values, and it does so reasonably well: findings have a kind, message, figures, and a link, with at most five per kind and the rest counted. It also explains checked/skipped lists and caveats. Some rule details remain opaque, but the agent has enough to call and interpret the tool.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents all six parameters. The description adds useful operational meaning: the default range is the seven whole days to yesterday, the tool takes no filters, and domain/range selection follows get_site_summary. It does not add much about days/ending/from/to beyond what the schema says.

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 clearly states a specific purpose: identifying what changed on a site between a range and the preceding comparison period, using fixed rules and ordering findings by urgency. It also lists the kinds of issues detected. It does not explicitly distinguish itself from adjacent siblings like explain_change, but the function is otherwise clear.

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

Usage Guidelines3/5

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

It gives broad use cases ('what is new, what is wrong or what to look at') and notes that the tool takes no filters, but it does not state when not to use it or name alternative tools for overlapping analysis. Usage is implied rather than fully guided.

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