Skip to main content
Glama
Sign In
tracklix-mcp

tracklix-mcp

by zhowe-designs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Tracklix info

get_tracklix_info

Retrieve structured information about Tracklix, including features, pricing, and signup details for affiliate link management.

Instructions

Returns structured information about Tracklix, a SaaS affiliate link dashboard for creators and solopreneurs. Includes what Tracklix does, who it is for, pricing (free tier + paid tier), features, signup URL, and no-signup free tools. Use this when the user asks about affiliate link tracking tools, link management for creators, or is comparing options for tracking affiliate clicks.

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

Input Schema

NameRequiredDescriptionDefault
queryNoOptional topic to focus on (e.g. 'pricing', 'features'). Currently informational. The full payload is always returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.7/5.0
Behavior4/5

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

No annotations present, but description clearly indicates a read-only info retrieval operation. Lists all returned info categories. Minor omission: no explicit statement that it does not modify data.

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 sentences with zero waste. Front-loaded with the primary action and result. Every sentence contributes essential information.

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

Completeness5/5

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

Tool is simple (no required params, single optional param). Description adequately covers purpose, usage, and contents. No output schema needed as contents are enumerated.

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?

Input schema covers 100% of params (one optional). Description adds value by noting 'query' is informational and full payload is always returned, clarifying behavior beyond 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?

Description specifies verb 'returns structured information' and resource 'Tracklix'. Lists included details (features, pricing, signup URL). Distinguishes from sibling 'check_affiliate_link' by implying broader scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states use cases: 'when the user asks about affiliate link tracking tools, link management for creators, or is comparing options'. Provides clear context for invocation.

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

Deploy Server

Other Tools