Skip to main content
Glama

tanstack_ecosystem

Filter and list TanStack ecosystem partners by category or library. Find tools for auth, database, deployment, monitoring, and more.

Instructions

List TanStack ecosystem partners (auth, database, deployment, monitoring, etc.) with optional category/library filters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoFilter by category (e.g. auth, database, deployment, monitoring, api, code-review)
libraryNoFilter by TanStack library (e.g. start, query, table)

Implementation Reference

  • src/index.ts:271-295 (registration)
    The tool 'tanstack_ecosystem' is registered here via server.tool() with name 'tanstack_ecosystem' and its description/schema.
    // 7. tanstack_ecosystem
    server.tool(
      "tanstack_ecosystem",
      "List TanStack ecosystem partners (auth, database, deployment, monitoring, etc.) with optional category/library filters",
      {
        category: z
          .string()
          .optional()
          .describe(
            "Filter by category (e.g. auth, database, deployment, monitoring, api, code-review)",
          ),
        library: z
          .string()
          .optional()
          .describe("Filter by TanStack library (e.g. start, query, table)"),
      },
      async ({ category, library }) => {
        const args = ["ecosystem", "--json"];
        if (category) args.push("--category", category);
        if (library) args.push("--library", library);
    
        const { stdout } = await runCli(args);
        return jsonResult(parseJsonOutput(stdout));
      },
    );
  • The handler function that executes the tool logic: builds CLI args (ecosystem, --json, optional --category and --library), runs the CLI, and returns the parsed JSON result.
    async ({ category, library }) => {
      const args = ["ecosystem", "--json"];
      if (category) args.push("--category", category);
      if (library) args.push("--library", library);
    
      const { stdout } = await runCli(args);
      return jsonResult(parseJsonOutput(stdout));
    },
  • Input schema using Zod for the tool: optional 'category' (string) and optional 'library' (string) parameters.
    {
      category: z
        .string()
        .optional()
        .describe(
          "Filter by category (e.g. auth, database, deployment, monitoring, api, code-review)",
        ),
      library: z
        .string()
        .optional()
        .describe("Filter by TanStack library (e.g. start, query, table)"),
    },
  • The runCli helper that executes the TanStack CLI via npx @tanstack/cli, used by the tool handler.
    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() };
    }
  • Helper functions parseJsonOutput and jsonResult used by the tool handler to parse and format CLI output.
    function parseJsonOutput(stdout: string): unknown {
      // The CLI may print warnings before the JSON blob – find the first { or [
      const jsonStart = stdout.search(/[\[{]/);
      if (jsonStart === -1) {
        throw new Error(`CLI returned non-JSON output:\n${stdout}`);
      }
      return JSON.parse(stdout.slice(jsonStart));
    }
    
    function textResult(text: string) {
      return { content: [{ type: "text" as const, text }] };
    }
    
    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 provided, and the description only says 'List' without disclosing behavioral traits like read-only nature, rate limits, pagination, or what happens with no filters. The agent is left guessing about operation safety and side effects.

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?

Single sentence, front-loaded with main action, no unnecessary words. Every part earns its place.

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?

Adequate for a simple list tool with filters, but missing output description (e.g., what fields are returned). No output schema, so description should clarify return format. Otherwise complete enough for basic use.

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% (both params described in schema). The description adds no extra meaning beyond the schema; baseline 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 'List' and resource 'TanStack ecosystem partners' with optional filters, distinguishing it from sibling tools like listTanStackAddOns and tanstack_search_docs which target different resources.

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 when-to-use or when-not-to-use guidance relative to sibling tools. The description does not mention alternatives or context for choosing this tool over listTanStackAddOns or other list tools.

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