Skip to main content
Glama

get_schema_info

Retrieve details about Vega-Lite schema properties like mark, encoding, data, or transform to understand visualization specifications and structure.

Instructions

Get information about Vega-Lite schema properties and structure

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
propertyNoSchema property to get information about (e.g., 'mark', 'encoding', 'data', 'transform')

Implementation Reference

  • Handler for the 'get_schema_info' tool, currently a stub that returns a message indicating it needs to be implemented.
    case "get_schema_info": {
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              message: "Schema info tool - to be implemented",
              property: args?.property || "all",
            }, null, 2),
          },
        ],
      };
    }
  • src/index.ts:81-94 (registration)
    Registration of the 'get_schema_info' tool in the ListTools response, including name, description, and input schema.
    {
      name: "get_schema_info",
      description: "Get information about Vega-Lite schema properties and structure",
      inputSchema: {
        type: "object",
        properties: {
          property: {
            type: "string",
            description: "Schema property to get information about (e.g., 'mark', 'encoding', 'data', 'transform')",
          },
        },
        additionalProperties: false,
      },
    },
  • Input schema definition for the 'get_schema_info' tool.
    inputSchema: {
      type: "object",
      properties: {
        property: {
          type: "string",
          description: "Schema property to get information about (e.g., 'mark', 'encoding', 'data', 'transform')",
        },
      },
      additionalProperties: false,
    },
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 only states the tool's purpose without detailing behavioral traits such as whether it's read-only, if it requires authentication, rate limits, error handling, or what the output format might be. For a tool with no annotations, this is a significant gap in transparency.

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, clear sentence that efficiently conveys the tool's purpose without unnecessary words. It is front-loaded with the core action and resource, making it easy to understand at a glance. Every part of the sentence earns its place by specifying the tool's function.

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 the complexity of a tool that retrieves schema information, the description is incomplete. There are no annotations to clarify behavior, no output schema to explain return values, and the description lacks details on what 'information' includes (e.g., property types, constraints, examples). This makes it inadequate for an agent to fully understand how to use the tool 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?

The input schema has 100% description coverage, with the single parameter 'property' documented as 'Schema property to get information about (e.g., 'mark', 'encoding', 'data', 'transform').' The description does not add any additional meaning beyond this, such as syntax details or usage examples. Given the high schema coverage, the baseline score of 3 is appropriate.

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 as 'Get information about Vega-Lite schema properties and structure,' specifying both the action ('Get information') and the resource ('Vega-Lite schema properties and structure'). However, it does not explicitly differentiate from sibling tools like 'get_example' or 'search_docs,' which might also relate to Vega-Lite documentation or validation, so it lacks sibling differentiation for a perfect score.

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 does not mention sibling tools like 'get_example' or 'search_docs,' nor does it specify contexts, prerequisites, or exclusions for usage. This leaves the agent without clear direction on tool selection.

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/inteligencianegociosmmx/vegaLite_mcp_server'

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