Skip to main content
Glama

Verify Tracking Installation

verify_tracking_installation
Read-onlyIdempotent

Return tracking verification signals and the next recommended setup action. Checks the published campaign site for the AffiliateBase script and a Stripe checkout it tags, so an install can be confirmed ready without a test purchase.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
okYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint, and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context: it inspects two specific artifacts (the published site's script and the Stripe checkout it tags) and returns both verification signals and a recommended next setup action. Minor tension exists between "checks the published campaign site" and openWorldHint=false, but the site is a bounded, platform-managed resource, not an open web search.

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?

Two tight sentences with the outcome front-loaded (verification signals plus next action) followed by the mechanism. Every clause carries information; nothing is redundant with the name or 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 zero parameters, rich annotations, and an output schema covering return values, the description only needs to explain what is inspected and what the agent gets back, which it does. It could go slightly further on preconditions (e.g., whether the campaign site must be published for a meaningful result).

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 zero parameters and the schema is empty at 100% coverage, so there is nothing for the description to compensate for. Baseline 4 applies; the description correctly avoids inventing parameter semantics.

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?

Names a specific verb (verify) and resource (tracking installation), then concretizes it: checks the published campaign site for the AffiliateBase script and a Stripe checkout it tags. This implicitly separates it from adjacent setup tools like get_test_affiliate_link and read_setup_status, though it never names a sibling explicitly.

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?

"so an install can be confirmed ready without a test purchase" gives a clear usage condition and effectively names the alternative path (a test purchase) that this tool replaces. There is no explicit when-not-to-use statement, but the context is clear enough to select the tool.

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