Skip to main content
Glama
Sign In
CommerceHub MCP

CommerceHub MCP

by spirit122
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

analytics_conversion

Provides conversion analytics for e-commerce platforms, helping agents track and optimize sales performance. Requires a higher plan.

Instructions

[UPGRADE REQUERIDO] Esta herramienta requiere un plan superior - usa "license_status" para ver opciones

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.2

TDQS

C2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does disclose a prerequisite (higher plan required), which is somewhat transparent, but it omits any behavioral traits like what the tool does, side effects, or error cases.

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

Conciseness4/5

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

The description is a single sentence, concise and front-loaded. It earns its place by conveying the upgrade requirement, though it sacrifices any functional detail.

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

Completeness1/5

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

Given the tool has no annotations, no output schema, and no parameter details, the description must provide context. It only mentions a license gate, leaving the agent unable to determine if this tool is relevant for a conversion-analytics task.

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 has zero parameters, so the schema already fully covers this dimension. Description adds nothing, but none is needed; baseline 4 for 0-parameter tools.

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

Purpose1/5

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

The description only says an upgrade is required, never stating what analytics_conversion does. The name hints at conversion analytics, but no verb or resource is described, leaving the tool's purpose entirely unclear.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool instead of alternatives. The only direction is to use license_status to see upgrade options, which is about licensing, not usage.

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