Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Check the tracking

tracking_check
Read-onlyIdempotent

Shows page views in the last 24 hours and visitors online now. testVisit true opens the actual website in a fresh browser and confirms that its installed tracker received a page-view receipt for this site. It never injects missing tracking code or sends a fabricated event directly to the collector. Consent banners, bot protection, unpublished changes or a blocked script can prevent confirmation. A test visit is limited to once per site every 30 seconds. sendTestEvent is a deprecated alias for testVisit.

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": {
      "siteId": "<siteId>"
    },
    "name": "tracking_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYes
testVisitNo
sendTestEventNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Strong disclosure beyond the annotations: it says a test visit opens the real site in a fresh browser and confirms receipt, explicitly states it never injects missing tracking code or fabricates events, and discloses the once-per-30-seconds limiter. Annotations already cover read-only/idempotent/open-world, and the description adds the meaningful side-effect profile; the only gap is not saying what the result looks like on failure.

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

Conciseness5/5

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

Front-loaded with the primary output, then the testVisit semantics, then the failure modes and rate limit; every sentence adds information an agent needs. No filler or restatement of the title.

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 should ideally state the shape of the test-visit confirmation (boolean vs receipt details), which is only implied by 'confirms'. Otherwise it is complete for a three-parameter diagnostic tool, covering rate limits, side effects, and failure modes.

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 description coverage is 0%, so the description must carry the load, and it defines testVisit's effect and flags sendTestEvent as a deprecated alias, which is essential to avoid misuse. siteId is left entirely unexplained, a minor gap given it is required.

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 names specific outputs (page views in the last 24 hours, visitors online now) and explains the testVisit diagnostic path, so the resource and verb are concrete. It falls short of 5 because the tool's dual identity (a stats read plus an active browser-based tracker test) is not framed up front against siblings like analytics_getRealtime.

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 clear context for when testVisit is warranted and when confirmation can fail (consent banners, bot protection, unpublished changes, blocked scripts), which is useful. However it never states when to prefer this over a sibling such as analytics_getRealtime for the same page-view numbers, and offers no explicit exclusions.

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