Skip to main content
Glama
Sign In

Measure.events Analytics

by io.github.meetclawdius
OverviewDiscussionsAdmin

7-day summary

get_site_summary
Read-only

A plain-language summary of the last 7 days with week-over-week change and highlights.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site_key": "<site_key>"
    },
    "name": "get_site_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_keyYesThe site's tracking ID (site_key), from list_sites.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / site_key / description
      Previous value: -"The site's tracking ID"New value: +"The site's tracking ID (site_key), from list_sites."
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description usefully adds that the output is plain-language and includes week-over-week comparison and highlights. It stops short of saying whether data is live vs cached, how 'highlights' are chosen, or what the response shape actually is.

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?

One efficient sentence with no filler and the time window front-loaded. Slightly undermined by vague terms ('plain-language', 'highlights') that could have been traded for concrete detail.

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?

With no output schema, the description is the only source of return-value information, and it gives a rough shape (summary + WoW change + highlights) without enough specificity for an agent to know what it will actually get back. Adequate for a read-only summarizer, but not complete.

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 coverage is 100% and the single parameter site_key is explicitly documented as coming from list_sites, so the schema carries the burden. The description adds nothing about the parameter, which is the expected baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the output (a plain-language 7-day summary with week-over-week change and highlights) but never states the resource — the site is only implied by the tool name — and it does nothing to separate this from siblings like get_insights, get_site_analytics, or get_breakdown, which plausibly return overlapping data.

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?

It gives no condition for when to pick this over get_insights or get_site_analytics, and no prerequisites beyond the schema-mandated site_key. The agent must infer selection from the name alone.

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

All Measure.events Analytics 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