Skip to main content
Glama

searchProducts

Find products in ZenTao project management system by keyword to quickly locate relevant items for tracking and management tasks.

Instructions

Search products by keyword; returns a short list of products.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordNoKeyword to match product name
limitNoMax items

Implementation Reference

  • Handler function that destructures arguments, calls the listProducts helper, and returns the products as JSON in the MCP response format.
    if (name === "searchProducts") {
      const { keyword, limit } = args;
      const products = await listProducts({ keyword, limit });
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({ products }, null, 2),
          },
        ],
      };
    }
  • Tool registration in the listTools response, including name, description, and input schema.
    {
      name: "searchProducts",
      description: "Search products by keyword; returns a short list of products.",
      inputSchema: {
        type: "object",
        properties: {
          keyword: { type: "string", description: "Keyword to match product name" },
          limit: { type: "number", description: "Max items", default: 20 },
        },
        required: [],
        additionalProperties: false,
      },
    },
    {
  • Input schema defining parameters for keyword and optional limit.
      inputSchema: {
        type: "object",
        properties: {
          keyword: { type: "string", description: "Keyword to match product name" },
          limit: { type: "number", description: "Max items", default: 20 },
        },
        required: [],
        additionalProperties: false,
      },
    },
  • Core helper function that fetches products from ZenTao API, filters by keyword if provided, and limits results.
    async function listProducts({ keyword, limit = 20 } = {}) {
      const res = await callZenTao({
        path: "products",
        query: { page: 1, limit, keywords: keyword },
      });
      const products = extractArray(res.data, ["products"]);
      const filtered = keyword
        ? products.filter((p) =>
            `${p.name || ""}`.toLowerCase().includes(keyword.toLowerCase())
          )
        : products;
      return filtered.slice(0, limit);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool returns 'a short list of products,' but lacks details on permissions, rate limits, error handling, or what 'short' means (e.g., pagination, default behavior). This is a significant gap for a search tool.

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 extremely concise and front-loaded: two clauses that directly state the action and outcome with zero wasted words. Every sentence earns its place by covering core functionality efficiently.

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 low complexity (2 parameters, no output schema, no annotations), the description is minimally complete but lacks depth. It covers the basic purpose and return type but misses behavioral context needed for effective use, such as result format or limitations.

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%, so the schema already documents both parameters ('keyword' and 'limit') adequately. The description adds no additional meaning beyond implying keyword matching, aligning with the baseline for high schema coverage.

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: 'Search products by keyword; returns a short list of products.' It specifies the verb ('Search'), resource ('products'), and scope ('by keyword'), but does not differentiate from siblings (none are product-related).

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 mentions no prerequisites, exclusions, or comparisons to sibling tools (which are unrelated to products), leaving usage context implied at best.

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/Valiant-Cat/zentao-mcp-server'

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