Skip to main content
Glama

Ad Spec Guard

validate_utm

Read-only

Inspect the UTM parameters already on a URL and report missing required parameters and values that will fragment reporting, such as mixed case or encoded spaces. Does not rewrite the URL.

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": {
      "url": "<url>"
    },
    "name": "validate_utm"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe tagged URL to inspect.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, non-destructive, non-open-world check, so the description does not need to re-explain safety. It adds useful behavioral detail by saying it reports missing required parameters and specific value problems that fragment reporting, and it reinforces that the URL is not modified.

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?

The description is two focused sentences with the main action and scope front-loaded. The second sentence is short and explicitly prevents a likely misunderstanding about rewriting the URL, so every sentence earns its place.

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?

For a simple one-parameter, read-only validation tool with annotations covering safety, the description is largely complete. It explains what is checked and what kinds of problems are reported, though it could go slightly further by clarifying where 'required' parameters come from or what the report contains.

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?

The single url parameter is fully described in the schema as 'The tagged URL to inspect,' so the schema already carries parameter meaning. The description adds context about inspecting existing UTM parameters but does not contribute additional URL format or validation syntax beyond the schema.

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

Purpose5/5

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

The description states a specific verb and resource: inspect UTM parameters already present on a URL and report missing or reporting-fragmenting values. It adds concrete examples of the problems found, such as mixed case and encoded spaces, and clearly distinguishes the tool from a URL builder by saying it does not rewrite the URL.

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 clearly indicates the usage context: checking tagging on an existing URL rather than constructing one. The phrase 'Does not rewrite the URL' usefully excludes build-style behavior, though it does not explicitly name a sibling tool or state all when-not conditions.

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.