Skip to main content
Glama
Sign In
Launch Engine

Launch Engine

by ZionHopkins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

traffic_analytics

Read-only

Analyze traffic sources and attribute conversions to channels by inputting a market slug. Generate performance reports to inform marketing decisions.

Instructions

Traffic Analytics & Attribution — performance reporting and attribution.

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": {
      "market_name": "<market_name>"
    },
    "name": "traffic_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
market_nameYesThe market/pipeline slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating a safe read operation. The description adds no further behavioral context beyond stating it is for reporting and attribution, which aligns with annotations but does not disclose any additional traits like performance characteristics or data scope.

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

Conciseness3/5

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

The description is very short (one line), but it is vague and does not provide enough substance to fully justify its length. While not overly verbose, it lacks clarity and does not effectively communicate the tool's purpose.

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

Completeness3/5

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

Given the tool's low complexity (one parameter, no nested objects), annotations present, and no output schema, the description is adequate but incomplete. It does not explain what the reporting or attribution outputs entail, leaving the agent without full context of the tool's behavior.

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?

Input schema has one required parameter 'market_name' with a description 'The market/pipeline slug'. Schema coverage is 100%, so the description adds no extra meaning beyond what the schema already provides.

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

Purpose3/5

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

The description mentions 'Traffic Analytics & Attribution — performance reporting and attribution', which indicates a verb (reporting/analytics) and a resource (traffic), but is vague and does not clearly distinguish from sibling tools like 'traffic_strategy'.

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 on when to use this tool versus alternatives such as 'traffic_strategy' or other reporting tools. The description lacks any when-to-use or when-not-to-use context.

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