Skip to main content
Glama
hackle-io

hackle-mcp

Official
by hackle-io

analytics-chart-detail

Fetch and visualize detailed analytics from A/B test charts by providing chart ID and type using the hackle-mcp server's tool.

Instructions

fetch analytics chart detail. You can visualize the chart using this tool's result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chartIdYesChart id
chartTypeYesType of the chart. Will throw an error if given chartId's chart type is different from chartType.

Implementation Reference

  • The handler function for the 'analytics-chart-detail' tool. It constructs a query string with chartType, fetches the chart details from the API using WebClient.get, stringifies the JSON response, and returns it as text content.
    async ({ chartId, chartType }) => {
      const qs = stringify({ chartType }, { addQueryPrefix: true });
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(await WebClient.get(`/api/v1/analytics/charts/${chartId}${qs}`)),
          },
        ],
      };
    },
  • Input schema defined using Zod: requires chartId (positive number) and chartType (one of FUNNEL, DATA_INSIGHT, RETENTION, USER_PATH).
    {
      chartId: z.number().positive().describe('Chart id'),
      chartType: z
        .enum(['FUNNEL', 'DATA_INSIGHT', 'RETENTION', 'USER_PATH'])
        .describe("Type of the chart. Will throw an error if given chartId's chart type is different from chartType."),
    },
  • src/index.ts:291-312 (registration)
    The server.tool call that registers the 'analytics-chart-detail' tool, providing the name, description, input schema, and inline handler function.
    server.tool(
      'analytics-chart-detail',
      "fetch analytics chart detail. You can visualize the chart using this tool's result.",
      {
        chartId: z.number().positive().describe('Chart id'),
        chartType: z
          .enum(['FUNNEL', 'DATA_INSIGHT', 'RETENTION', 'USER_PATH'])
          .describe("Type of the chart. Will throw an error if given chartId's chart type is different from chartType."),
      },
      async ({ chartId, chartType }) => {
        const qs = stringify({ chartType }, { addQueryPrefix: true });
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(await WebClient.get(`/api/v1/analytics/charts/${chartId}${qs}`)),
            },
          ],
        };
      },
    );
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions fetching details and visualization, but doesn't disclose critical behaviors: whether this is a read-only operation, potential errors (e.g., from mismatched chartType), rate limits, authentication needs, or what the result format looks like. The visualization hint is useful but insufficient for a tool with no annotation coverage.

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 concise with two sentences that are front-loaded: the first states the core action, and the second adds a usage hint. There's no unnecessary repetition or fluff, though it could be more informative. It earns its place but leaves gaps in completeness.

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 no annotations, no output schema, and a tool that fetches details (likely involving data retrieval), the description is incomplete. It doesn't explain the return value format, error conditions, or how the visualization hint translates to practical use. For a 2-parameter tool with siblings, more context is needed to guide the agent effectively.

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 already documents both parameters (chartId and chartType) with descriptions and enum values. The description adds no additional meaning beyond what's in the schema, such as explaining how chartId is obtained or the implications of chartType matching. Baseline 3 is appropriate when schema does the heavy lifting.

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 states 'fetch analytics chart detail' which provides a basic verb+resource combination, but it's vague about what 'detail' includes (e.g., configuration, data, metadata). It doesn't clearly distinguish from siblings like 'analytics-chart-list' (which presumably lists charts) or 'data-report-detail' (which might have overlapping functionality). The second sentence about visualization adds some context but doesn't clarify the core purpose.

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 explicit guidance on when to use this tool versus alternatives is provided. The description mentions visualization, which might imply use for rendering charts, but it doesn't specify prerequisites (e.g., needing a valid chartId) or exclusions (e.g., not for creating charts). Without comparison to siblings like 'analytics-chart-list' or 'data-report-detail', the agent lacks clear direction.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hackle-io/hackle-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server