Skip to main content
Glama

getAddOnDetails

Retrieve files, dependencies, options, and routes for a TanStack Start add-on using its identifier and optional framework.

Instructions

Get detailed information about a specific TanStack Start add-on (files, dependencies, options, routes)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addonIdYesAdd-on identifier (e.g. drizzle, clerk, shadcn, prisma, sentry)
frameworkNoProject frameworkReact

Implementation Reference

  • src/index.ts:82-108 (registration)
    Tool 'getAddOnDetails' is registered via server.tool() on the McpServer instance (line 83). It is the second tool in the server definition, registered with the name 'getAddOnDetails'.
    // 2. getAddOnDetails
    server.tool(
      "getAddOnDetails",
      "Get detailed information about a specific TanStack Start add-on (files, dependencies, options, routes)",
      {
        addonId: z
          .string()
          .describe(
            "Add-on identifier (e.g. drizzle, clerk, shadcn, prisma, sentry)",
          ),
        framework: z
          .enum(["React", "Solid"])
          .default("React")
          .describe("Project framework"),
      },
      async ({ addonId, framework }) => {
        const { stdout } = await runCli([
          "create",
          "--addon-details",
          addonId,
          "--framework",
          framework,
          "--json",
        ]);
        return jsonResult(parseJsonOutput(stdout));
      },
    );
  • The handler function for getAddOnDetails. It executes the TanStack CLI with args ['create', '--addon-details', addonId, '--framework', framework, '--json'], parses the JSON output, and returns it as a text result.
    async ({ addonId, framework }) => {
      const { stdout } = await runCli([
        "create",
        "--addon-details",
        addonId,
        "--framework",
        framework,
        "--json",
      ]);
      return jsonResult(parseJsonOutput(stdout));
    },
  • Input schema for getAddOnDetails defining two parameters: 'addonId' (string, required) and 'framework' (enum ['React','Solid'], defaults to 'React').
    {
      addonId: z
        .string()
        .describe(
          "Add-on identifier (e.g. drizzle, clerk, shadcn, prisma, sentry)",
        ),
      framework: z
        .enum(["React", "Solid"])
        .default("React")
        .describe("Project framework"),
    },
  • The runCli helper that executes the CLI command (npx @tanstack/cli create --addon-details ...) via execFileAsync. Used by the handler to invoke the underlying TanStack CLI.
    async function runCli(
      args: string[],
      timeoutMs = 60_000,
    ): Promise<{ stdout: string; stderr: string }> {
      const { stdout, stderr } = await execFileAsync(
        TANSTACK_CLI,
        [...TANSTACK_ARGS, ...args],
        {
          timeout: timeoutMs,
          maxBuffer: 10 * 1024 * 1024, // 10 MB
          env: { ...process.env, NO_COLOR: "1" },
        },
      );
      return { stdout: stdout.trim(), stderr: stderr.trim() };
    }
  • The jsonResult helper wraps data in the MCP text content format after JSON serialization. Used by the handler to format the CLI output as a tool result.
    function textResult(text: string) {
      return { content: [{ type: "text" as const, text }] };
    }
    
    function jsonResult(data: unknown) {
      return textResult(JSON.stringify(data, null, 2));
    }
Behavior3/5

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

No annotations exist, so the description is the sole source. It indicates a read operation (no destruction), but does not disclose authentication needs, rate limits, or return structure details beyond listing some attributes.

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 one concise sentence with a parenthetical list, front-loading the purpose. Every word is necessary and clear.

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 output schema, the description should clarify the structure and content of the returned details. It only lists categories (files, dependencies, etc.) without explaining format or behavior in edge cases.

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 covers both parameters with descriptions and examples. The tool description does not add meaning beyond what the schema provides, so baseline of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the verb 'Get detailed information', specifies the resource 'TanStack Start add-on', and lists what details (files, dependencies, options, routes). This distinguishes it from sibling tools like listTanStackAddOns.

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

Usage Guidelines3/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 vs. alternatives like listTanStackAddOns. The name and description imply detailed lookup, but no when-not or exclusion criteria are provided.

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/zPeppOz/tanstack-mcp'

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