Skip to main content
Glama
Sign In

Brent Burgess

by com.brentburgess
OverviewDiscussionsAdmin

This site’s own numbers

get_site_stats
Read-onlyIdempotent

The figures on this site’s data page: browser page views and font downloads since launch, crawlers and scans in the latest complete week, commits, pull requests, CI runs and how long a merged change takes to go live, and the nightly pipeline’s tests and sources, each with the last day the data covers. For the tables behind them, use query_dataset.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
urlYesThe page that shows them
monthlyYesWhen the next monthly page and country counts appear
readingYesReading the site, since launch
buildingYesBuilding the site
datasetsYesThe tables behind the numbers
pipelineYesThe nightly pipeline
see_alsoYesPages with numbers this server does not return
automatedYesCrawlers, bots and scans
data_throughYesThe last day the numbers cover

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / building / properties / merge_to_live / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "median_minutes": {
-        "description": "Median minutes from a merge to the end of the deploy that put it live",
-        "minimum": 0,
-        "type": "number"
-      },
-      "merges": {
-        "description": "Merged pull requests a deploy has put live since then",
-        "maximum": 9007199254740991,
-        "minimum": 0,
-        "type": "integer"
-      },
-      "since": {
-        "description": "The first day counted, when deploys became automatic",
-        "maxLength": 10,
-        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
-        "type": "string"
-      }
-    },
-    "required": [
-      "since",
-      "merges",
-      "median_minutes"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "median_minutes": {
+        "description": "Median minutes from a merge to the end of the deploy that put it live",
+        "minimum": 0,
+        "type": "number"
+      },
+      "merges": {
+        "description": "Merged pull requests a deploy has put live since then",
+        "maximum": 9007199254740991,
+        "minimum": 0,
+        "type": "integer"
+      },
+      "since": {
+        "description": "The day of the first merge counted; deploys have been automatic since then",
+        "maxLength": 10,
+        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+        "type": "string"
+      }
+    },
+    "required": [
+      "since",
+      "merges",
+      "median_minutes"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
  2. Changed3 schema fields changed
    • addedOutput schema / properties / building / properties / merge_to_live
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "median_minutes": {
+          "description": "Median minutes from a merge to the end of the deploy that put it live",
+          "minimum": 0,
+          "type": "number"
+        },
+        "merges": {
+          "description": "Merged pull requests a deploy has put live since then",
+          "maximum": 9007199254740991,
+          "minimum": 0,
+          "type": "integer"
+        },
+        "since": {
+          "description": "The first day counted, when deploys became automatic",
+          "maxLength": 10,
+          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+          "type": "string"
+        }
+      },
+      "required": [
+        "since",
+        "merges",
+        "median_minutes"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "From merge to live, or null before the first merge went live"
+}
    • changedOutput schema / properties / building / required
      Previous value: -[
-  "commits",
-  "commits_with_claude",
-  "ci_runs",
-  "ci_passed",
-  "months",
-  "notes"
-]New value: +[
+  "commits",
+  "commits_with_claude",
+  "ci_runs",
+  "ci_passed",
+  "months",
+  "merge_to_live",
+  "notes"
+]
    • changedOutput schema / properties / datasets / items / properties / name / enum
      Previous value: -[
-  "agg_ci_steps_30d",
-  "agg_countries_monthly",
-  "agg_pages_monthly",
-  "fct_checks",
-  "fct_ci_daily",
-  "fct_crawlers_weekly",
-  "fct_font_daily",
-  "fct_github_monthly",
-  "fct_github_weekly",
-  "fct_pipeline_runs",
-  "fct_probes_weekly",
-  "fct_reading_daily"
-]New value: +[
+  "agg_ci_steps_30d",
+  "agg_countries_monthly",
+  "agg_pages_monthly",
+  "fct_checks",
+  "fct_ci_daily",
+  "fct_crawlers_weekly",
+  "fct_font_daily",
+  "fct_github_monthly",
+  "fct_github_weekly",
+  "fct_merge_to_live",
+  "fct_pipeline_runs",
+  "fct_probes_weekly",
+  "fct_reading_daily"
+]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for what it adds beyond them: time-window semantics such as 'since launch', 'the latest complete week', and 'each with the last day the data covers'. Those freshness details materially affect how an agent interprets the numbers. It stops short of describing staleness behavior or what happens if a pipeline has no data, which keeps it from a 5.

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?

It is a single front-loaded sentence that names the resource first and closes with the query_dataset hand-off, so every clause carries information about the returned metrics. The long comma-separated enumeration is dense to parse but each item genuinely describes a distinct output, so little could be cut without losing scope detail.

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?

With an output schema present, zero parameters, and full annotation coverage, the remaining burden is explaining what the figures represent and over what periods, which the description does explicitly. An agent can decide to call this, know what it will contain, and know which sibling to use for raw tables.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly avoids inventing scope options and instead spends its words on what the returned figures mean.

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 enumerates the exact figures returned: browser page views, font downloads, crawlers and scans, commits, pull requests, CI runs, merge-to-live time, and nightly pipeline tests and sources. That is far more specific than a restatement of the name, and it distinguishes the tool from query_dataset by framing this as the summary figures rather than the underlying tables. The only shortfall is that the verb is implicit ("the figures on this site's data page") rather than an explicit 'returns'.

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?

It gives one explicit routing rule: 'For the tables behind them, use query_dataset,' which tells the agent when a sibling is the better choice. It does not spell out positive when-to-use triggers (e.g., 'call this first for a site overview'), but with zero parameters and a self-evident purpose that is a small gap.

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

All Brent Burgess 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