Skip to main content
Glama

listTanStackAddOns

List available TanStack Start add-ons for React or Solid frameworks to extend your project.

Instructions

List all available TanStack Start add-ons for a given framework

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
frameworkNoProject frameworkReact

Implementation Reference

  • src/index.ts:60-62 (registration)
    Registers the 'listTanStackAddOns' tool on the MCP server with its name.
    // 1. listTanStackAddOns
    server.tool(
      "listTanStackAddOns",
  • Defines the input schema for listTanStackAddOns: accepts an optional 'framework' parameter (enum: React/Solid, default React).
    "List all available TanStack Start add-ons for a given framework",
    {
      framework: z
        .enum(["React", "Solid"])
        .default("React")
        .describe("Project framework"),
    },
  • Handler function that runs `npx @tanstack/cli create --list-add-ons --framework <framework> --json`, parses the JSON output, and returns it.
    async ({ framework }) => {
      const { stdout } = await runCli([
        "create",
        "--list-add-ons",
        "--framework",
        framework,
        "--json",
      ]);
      return jsonResult(parseJsonOutput(stdout));
    },
  • runCli helper used by the handler to execute the CLI command.
    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() };
    }
  • jsonResult helper used to format the JSON response.
    function jsonResult(data: unknown) {
      return textResult(JSON.stringify(data, null, 2));
    }
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only states the basic action and parameter, omitting details like read-only nature, authentication needs, or return format. Minimal behavioral context is given.

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 sentence with no unnecessary words. It is as concise as possible while conveying the core purpose.

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

Completeness4/5

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

For a simple list tool with one enum parameter and no output schema, the description is largely sufficient. It could be improved by hinting at the return format (e.g., names or IDs), but overall it is adequate for an agent to understand the tool.

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 coverage is 100% and describes the parameter as 'Project framework' with enum values. The description adds that the list is 'for a given framework', which is slightly redundant. No additional meaning beyond the schema.

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 tool lists TanStack Start add-ons for a given framework. The verb 'list' and resource 'add-ons' are specific. It distinguishes from siblings like createTanStackApplication (create) and getAddOnDetails (details).

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?

The description implies usage to view available add-ons but does not explicitly state when to use this tool versus alternatives like getAddOnDetails or tanstack_list_libraries. No 'when not to use' guidance is 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