lazymac-mcp

url_shortener

Shorten URLs with click tracking and geographic statistics for analytics, featuring sub-10ms redirects for performance.

Instructions

Shorten URLs with click tracking, geo stats, sub-10ms redirects

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

Input Schema

Name	Required	Description	Default
`params`	No	Free-form params object — passed as query string for GET, JSON body for POST

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 15, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions performance ('sub-10ms redirects') and analytics features (click tracking, geo stats), but lacks details on permissions, rate limits, error handling, or output format, which are critical for a tool that modifies URLs.

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 extremely concise and front-loaded, using a single sentence with no wasted words. Every phrase ('Shorten URLs', 'click tracking', 'geo stats', 'sub-10ms redirects') adds value by specifying functionality.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a URL shortener with analytics and no annotations or output schema, the description is incomplete. It omits details on required inputs, return values, error cases, and operational constraints, leaving significant gaps for an AI agent.

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 description coverage is 100%, so the schema documents the single parameter ('params' as a free-form object). The description adds no parameter-specific information beyond what's in the schema, resulting in a baseline score of 3.

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 clearly states the tool's function ('Shorten URLs') and mentions key features (click tracking, geo stats, sub-10ms redirects). It's specific about the verb and resource, but doesn't explicitly differentiate from sibling tools, which are unrelated to URL shortening.

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?

No guidance is provided on when to use this tool versus alternatives. The description lists features but doesn't indicate scenarios, prerequisites, or comparisons with other URL shorteners or related tools.

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