Skip to main content
Glama

get-visualization-tool-help

Access detailed usage information and examples for creating charts, diagrams, QR codes, and other visualizations with QuickChart.io tools.

Instructions

Get detailed usage information and examples for all available chart, diagram, and QR code tools

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the tool logic by returning JSON documentation of all visualization tools.
    export async function handleGetVisualizationToolHelpTool(
      args: any
    ): Promise<any> {
      try {
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(TOOL_DOCUMENTATION, null, 2),
            },
          ],
        };
      } catch (error) {
        throw new McpError(
          ErrorCode.InternalError,
          `Error getting visualization tools help: ${
            error instanceof Error ? error.message : String(error)
          }`
        );
      }
    }
  • The tool definition including name, description, and input schema (empty object).
    export const GET_VISUALIZATION_TOOL_HELP_TOOL: Tool = {
      name: "get-visualization-tool-help",
      description:
        "Get detailed usage information and examples for all available chart, diagram, and QR code tools",
      inputSchema: {
        type: "object",
        properties: {},
        additionalProperties: false,
      },
    };
  • Registration of the tool handler in the ALL_TOOL_HANDLERS mapping.
    "get-visualization-tool-help": {
      handler: handleGetVisualizationToolHelpTool,
      toolName: ToolNames.HELP,
    },
  • Registration of the tool in the ALL_TOOLS array.
    { tool: GET_VISUALIZATION_TOOL_HELP_TOOL, name: ToolNames.HELP },
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 of behavioral disclosure. It states the tool retrieves 'detailed usage information and examples,' implying a read-only, informational operation, but doesn't specify output format, data structure, or any constraints (e.g., rate limits, authentication needs). This leaves significant gaps in understanding how the tool behaves beyond its basic purpose.

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 a single, well-structured sentence that efficiently conveys the tool's purpose without unnecessary words. It is front-loaded with the key action ('Get detailed usage information and examples') and specifies the scope clearly. Every part of the sentence earns its place, making it highly concise and effective.

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 complexity (low, with 0 parameters) and the absence of annotations and output schema, the description is minimally adequate. It explains what the tool does but lacks details on behavioral traits, output format, or usage context. For a helper tool in a visualization-focused server, more guidance on when and how to use it would improve completeness, but it meets the basic threshold for a simple informational tool.

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 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately avoids mentioning any. A baseline of 4 is applied since no parameters exist, and the description doesn't introduce confusion by referencing non-existent inputs.

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 purpose: 'Get detailed usage information and examples for all available chart, diagram, and QR code tools.' It specifies the verb ('Get'), resource ('usage information and examples'), and scope ('all available chart, diagram, and QR code tools'). However, it doesn't explicitly differentiate from siblings like 'create-chart-using-natural-language' which might also provide guidance, so it doesn't reach the highest clarity level.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, timing (e.g., use before creating visualizations), or exclusions. For example, it doesn't clarify if this is for general reference or troubleshooting, leaving the agent to infer usage from context alone.

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

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/TakanariShimbo/quickchart-mcp-server'

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