Skip to main content
Glama

Tracking status

tracking_status
Read-onlyIdempotent

Is Motif still seeing this website? Last tracker event, last identified visitor, backend signup feed health, and the breakage alerts Motif's hourly check has open (tracker silent, signups silent or unmatched, visits dropped, Stripe or Search Console disconnected). An alert opens only once that check has recorded it, so judge the tracker by live and last_event_at too; empty alerts alone does not prove nothing is broken.

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": "tracking_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
website_idNowebsite id (uuid) or the site domain (example.com); omit when the account has one website

Output Schema

NameRequiredDescriptionDefault
liveYes
alertsYes
app_urlNo
last_event_atYes
server_milestonesNo
last_identified_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely non-obvious behavior: alerts only open once the hourly check has recorded them, implying detection latency, and it enumerates the specific alert conditions (tracker silent, signups silent/unmatched, visits dropped, Stripe/Search Console disconnected). It also names response fields to cross-check against, which is beyond what annotations provide.

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?

Two sentences, dense but purposeful, with the caveat about alert latency placed at the end where it belongs. Minor inefficiency: it leads with a rhetorical question instead of a direct statement of what the tool returns, and the parenthetical alert list is long.

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?

An output schema exists, so the description did not need to enumerate return fields, yet doing so usefully tells the agent which fields to cross-check for a verdict. Combined with the single well-documented parameter and full annotation coverage, an agent has enough to call it correctly; only explicit sibling routing is missing.

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?

There is a single optional parameter with 100% schema description coverage, including the uuid-or-domain format and the omit-when-single-website rule. The description adds nothing about website_id, so the schema does all the work and the baseline 3 applies.

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 opening question is indirect, but the tool's substance is stated concretely: last tracker event, last identified visitor, backend signup feed health, and open breakage alerts from Motif's hourly check. An agent can tell this is a per-website tracking/health diagnostic, though it never explicitly contrasts itself with siblings like analytics_snapshot or money_alerts.

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?

Usage is implied (use it to determine whether tracking is still firing and whether check-generated alerts exist) and it adds a real interpretive caveat: empty alerts alone do not prove nothing is broken, so judge the tracker by live and last_event_at too. However, no alternative tool is named and there is no explicit when-not-to-use guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources