fivebar

Read docs

read_docs

Read-onlyIdempotent

fivebar's own docs, as Markdown, for what a figure counts, how ranges, filters and goals work, how to install fivebar, or anything else the docs cover, with the page's address to give the user. topic names the page, which search_docs finds by its words; glossary is every rule the caveats of an answer are drawn from, and what each figure counts, in one answer. It reads fivebar's published docs alone, nothing of any site.

Input Schema

Name	Required	Description	Default
`topic`	Yes	The page. glossary: every rule the tools' caveats come from, and what each figure counts. metrics: what each figure counts. date-ranges: the presets and the period each is compared with. filters. panes: what each pane lists. goals. events. properties: custom properties. site-search: counting what visitors search a site for. sources-and-campaigns: how a source is named, tagged links, and channels. outbound-and-downloads. errors. error-pages. script-errors. ab-tests: comparing an A/B test's variants. speed. engagement: time on page and scroll depth. bots: what fivebar takes for a bot, which only get_site_bots's figures count, and the dashboard's Bots page. excluding-traffic: leaving a site's own visits out. public-stats. sites: a site's settings and time zone. sharing: inviting people to a site, and what each role may do. email-reports: a site's stats emailed each week or month. install. coding-assistants: instructions for one to add fivebar to a site. script-attributes. single-page-apps. proxy: sending the tag through the site's own domain. server-events: counting calls to an API or MCP server. platforms. checker: whether a site's home page has the tag, and its Content Security Policy. download-extensions. account. api: the API, for scripts: stats, adding and checking sites. mcp: connecting apps. privacy: the privacy policy, what fivebar keeps about visitors, account holders and their apps, and for how long. A link in a page read here to another of these pages is that topic.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 7, 2026

changedInput schema / properties / topic / description

Previous value: -"The page. glossary: every rule the tools' caveats come from, and what each figure counts. metrics: what each figure counts. date-ranges: the presets and the period each is compared with. filters. panes: what each pane lists. goals. events. properties: custom properties. site-search: counting what visitors search a site for. sources-and-campaigns: how a source is named, tagged links, and channels. outbound-and-downloads. error-pages. ab-tests: comparing an A/B test's variants. speed. engagement: time on page and scroll depth. bots: what fivebar takes for a bot, which only get_site_bots's figures count, and the dashboard's Bots page. excluding-traffic: leaving a site's own visits out. public-stats. sites: a site's settings and time zone. sharing: inviting people to a site, and what each role may do. email-reports: a site's stats emailed each week or month. install. coding-assistants: instructions for one to add fivebar to a site. script-attributes. single-page-apps. proxy: sending the tag through the site's own domain. server-events: counting calls to an API or MCP server. platforms. checker: whether a site's home page has the tag, and its Content Security Policy. download-extensions. account. api: the API, for scripts: stats, and listing, adding and checking sites. mcp: connecting apps. privacy: the privacy policy, what fivebar keeps about visitors, account holders and the apps they connect, and for how long. A link in a page read here to another of these pages is that topic."New value: +"The page. glossary: every rule the tools' caveats come from, and what each figure counts. metrics: what each figure counts. date-ranges: the presets and the period each is compared with. filters. panes: what each pane lists. goals. events. properties: custom properties. site-search: counting what visitors search a site for. sources-and-campaigns: how a source is named, tagged links, and channels. outbound-and-downloads. errors. error-pages. script-errors. ab-tests: comparing an A/B test's variants. speed. engagement: time on page and scroll depth. bots: what fivebar takes for a bot, which only get_site_bots's figures count, and the dashboard's Bots page. excluding-traffic: leaving a site's own visits out. public-stats. sites: a site's settings and time zone. sharing: inviting people to a site, and what each role may do. email-reports: a site's stats emailed each week or month. install. coding-assistants: instructions for one to add fivebar to a site. script-attributes. single-page-apps. proxy: sending the tag through the site's own domain. server-events: counting calls to an API or MCP server. platforms. checker: whether a site's home page has the tag, and its Content Security Policy. download-extensions. account. api: the API, for scripts: stats, adding and checking sites. mcp: connecting apps. privacy: the privacy policy, what fivebar keeps about visitors, account holders and their apps, and for how long. A link in a page read here to another of these pages is that topic."

changedInput schema / properties / topic / enum

Previous value: -[
-  "glossary",
-  "metrics",
-  "date-ranges",
-  "filters",
-  "panes",
-  "goals",
-  "events",
-  "properties",
-  "site-search",
-  "sources-and-campaigns",
-  "outbound-and-downloads",
-  "error-pages",
-  "ab-tests",
-  "speed",
-  "engagement",
-  "bots",
-  "excluding-traffic",
-  "public-stats",
-  "sites",
-  "sharing",
-  "email-reports",
-  "install",
-  "coding-assistants",
-  "script-attributes",
-  "single-page-apps",
-  "proxy",
-  "server-events",
-  "platforms",
-  "checker",
-  "download-extensions",
-  "account",
-  "api",
-  "mcp",
-  "privacy"
-]New value: +[
+  "glossary",
+  "metrics",
+  "date-ranges",
+  "filters",
+  "panes",
+  "goals",
+  "events",
+  "properties",
+  "site-search",
+  "sources-and-campaigns",
+  "outbound-and-downloads",
+  "errors",
+  "error-pages",
+  "script-errors",
+  "ab-tests",
+  "speed",
+  "engagement",
+  "bots",
+  "excluding-traffic",
+  "public-stats",
+  "sites",
+  "sharing",
+  "email-reports",
+  "install",
+  "coding-assistants",
+  "script-attributes",
+  "single-page-apps",
+  "proxy",
+  "server-events",
+  "platforms",
+  "checker",
+  "download-extensions",
+  "account",
+  "api",
+  "mcp",
+  "privacy"
+]

Changed2 schema fields changedOct 16, 2026

changedInput schema / properties / topic / description

Previous value: -"The page. glossary: every rule the tools' caveats come from, and what each figure counts. metrics: what each figure counts. date-ranges: the presets and the period each is compared with. filters. panes: what each pane lists. goals. events. properties: custom properties. site-search: counting what visitors search a site for. sources-and-campaigns: how a source is named, tagged links, and channels. outbound-and-downloads. error-pages. ab-tests: comparing an A/B test's variants. speed. engagement: time on page and scroll depth. bots: what fivebar takes for a bot, which only get_site_bots's figures count, and the dashboard's Bots page. excluding-traffic: leaving a site's own visits out. public-stats. sites: a site's settings and time zone. sharing: inviting people to a site, and what each role may do. email-reports: a site's stats emailed each week or month. install. coding-assistants: instructions for one to add fivebar to a site. script-attributes. single-page-apps. proxy: sending the tag through the site's own domain. platforms. checker: whether a site's home page has the tag, and its Content Security Policy. download-extensions. account. api: the API, for scripts: stats, and listing, adding and checking sites. mcp: connecting apps. privacy: the privacy policy, what fivebar keeps about visitors, account holders and the apps they connect, and for how long. A link in a page read here to another of these pages is that topic."New value: +"The page. glossary: every rule the tools' caveats come from, and what each figure counts. metrics: what each figure counts. date-ranges: the presets and the period each is compared with. filters. panes: what each pane lists. goals. events. properties: custom properties. site-search: counting what visitors search a site for. sources-and-campaigns: how a source is named, tagged links, and channels. outbound-and-downloads. error-pages. ab-tests: comparing an A/B test's variants. speed. engagement: time on page and scroll depth. bots: what fivebar takes for a bot, which only get_site_bots's figures count, and the dashboard's Bots page. excluding-traffic: leaving a site's own visits out. public-stats. sites: a site's settings and time zone. sharing: inviting people to a site, and what each role may do. email-reports: a site's stats emailed each week or month. install. coding-assistants: instructions for one to add fivebar to a site. script-attributes. single-page-apps. proxy: sending the tag through the site's own domain. server-events: counting calls to an API or MCP server. platforms. checker: whether a site's home page has the tag, and its Content Security Policy. download-extensions. account. api: the API, for scripts: stats, and listing, adding and checking sites. mcp: connecting apps. privacy: the privacy policy, what fivebar keeps about visitors, account holders and the apps they connect, and for how long. A link in a page read here to another of these pages is that topic."

changedInput schema / properties / topic / enum

Previous value: -[
-  "glossary",
-  "metrics",
-  "date-ranges",
-  "filters",
-  "panes",
-  "goals",
-  "events",
-  "properties",
-  "site-search",
-  "sources-and-campaigns",
-  "outbound-and-downloads",
-  "error-pages",
-  "ab-tests",
-  "speed",
-  "engagement",
-  "bots",
-  "excluding-traffic",
-  "public-stats",
-  "sites",
-  "sharing",
-  "email-reports",
-  "install",
-  "coding-assistants",
-  "script-attributes",
-  "single-page-apps",
-  "proxy",
-  "platforms",
-  "checker",
-  "download-extensions",
-  "account",
-  "api",
-  "mcp",
-  "privacy"
-]New value: +[
+  "glossary",
+  "metrics",
+  "date-ranges",
+  "filters",
+  "panes",
+  "goals",
+  "events",
+  "properties",
+  "site-search",
+  "sources-and-campaigns",
+  "outbound-and-downloads",
+  "error-pages",
+  "ab-tests",
+  "speed",
+  "engagement",
+  "bots",
+  "excluding-traffic",
+  "public-stats",
+  "sites",
+  "sharing",
+  "email-reports",
+  "install",
+  "coding-assistants",
+  "script-attributes",
+  "single-page-apps",
+  "proxy",
+  "server-events",
+  "platforms",
+  "checker",
+  "download-extensions",
+  "account",
+  "api",
+  "mcp",
+  "privacy"
+]

First observedOct 15, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world, so the safety profile is covered. The description adds value beyond them: output is Markdown, the response carries the page's address to hand to the user, and the tool is restricted to published docs rather than any site. It does not discuss size, truncation, or what a missing topic returns, keeping it below 5.

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

Conciseness3/5

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

Three sentences, but the first is a long run-on that stacks purposes and the return value in one breath before the routing rule appears. Nearly all content earns its place, yet the structure could be front-loaded more cleanly (what it does, then when to prefer search_docs).

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 one required, fully-enumerated parameter and no output schema, the description supplies what's missing: the return format (Markdown), the accompanying page address, and the closed scope. An agent can call it correctly without further inference; only edge behavior (invalid topic, oversized pages) is unaddressed.

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% and every one of the 36 enum values is documented, so the baseline is 3. The description still adds meaning: topics are the pages search_docs matches by words, and 'glossary is every rule the caveats of an answer are drawn from, and what each figure counts, in one answer' steers topic choice for caveat-heavy answers. That is genuine selection guidance beyond the enum list.

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?

States the resource ('fivebar's own docs, as Markdown') and enumerates the kinds of questions it answers (what a figure counts, ranges/filters/goals, install), plus the return shape (page address to give the user). It also distinguishes itself from search_docs by noting search_docs finds pages 'by its words'. The opening is slightly convoluted — the verb 'read' is only implied by the name — but the scope is unambiguous.

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

Usage Guidelines4/5

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

Gives an explicit routing rule to the sibling: 'topic names the page, which search_docs finds by its words', i.e. use search_docs when you don't already know the topic. It also states a hard boundary — 'It reads fivebar's published docs alone, nothing of any site' — which prevents misuse for site data. No explicit 'do not use for X' beyond that scope note, so not a full 5.

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

All fivebar tools Inspect

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

Need Help?