Skip to main content
Glama

list-category-objects

Retrieve all objects within a specific category from the PI Dashboard to organize and access related resources efficiently.

Instructions

List all objects for a specific category

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryIdYesCategory ID

Implementation Reference

  • build/index.js:741-759 (registration)
    Registration of the 'list-category-objects' tool, including inline schema and handler function.
    server.tool("list-category-objects", "List all objects for a specific category", {
        categoryId: z.number().describe("Category ID")
    }, async ({ categoryId }) => {
        try {
            const categoryObjects = await authenticatedRequest(`/categories/${categoryId}/categoryObjects`);
            return {
                content: [{
                        type: "text",
                        text: `Category objects retrieved successfully:\n${JSON.stringify(categoryObjects, null, 2)}`
                    }]
            };
        }
        catch (error) {
            return {
                isError: true,
                content: [{ type: "text", text: `Error fetching category objects: ${getErrorMessage(error)}` }]
            };
        }
    });
  • The main handler function that performs an authenticated API request to fetch category objects and returns the result as formatted text or an error message.
    }, async ({ categoryId }) => {
        try {
            const categoryObjects = await authenticatedRequest(`/categories/${categoryId}/categoryObjects`);
            return {
                content: [{
                        type: "text",
                        text: `Category objects retrieved successfully:\n${JSON.stringify(categoryObjects, null, 2)}`
                    }]
            };
        }
        catch (error) {
            return {
                isError: true,
                content: [{ type: "text", text: `Error fetching category objects: ${getErrorMessage(error)}` }]
            };
        }
    });
  • Input schema using Zod validation for the required 'categoryId' parameter.
    categoryId: z.number().describe("Category ID")
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states it's a list operation, implying read-only behavior, but doesn't cover critical aspects like pagination, rate limits, error handling, or what 'objects' entails (e.g., type, format). This leaves significant gaps for an agent to use it effectively.

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 with no wasted words. It's appropriately sized for a simple list tool and front-loads the essential action, making it efficient and easy to parse.

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 annotations and no output schema, the description is incomplete. It doesn't explain what 'objects' are returned, their structure, or any behavioral traits like pagination. For a tool with one parameter but undefined output, this lacks necessary context for reliable 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%, so the input schema fully documents the single parameter 'categoryId'. The description adds no additional meaning beyond implying it filters by category, which the schema already covers. This meets 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 verb ('List') and resource ('objects for a specific category'), making the purpose understandable. However, it doesn't distinguish this from sibling tools like 'list-categories' or 'list-charts', which would require more specificity to earn a 5.

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 like 'list-categories' or 'get-category', nor does it mention prerequisites such as authentication. It's a basic statement of function with no contextual usage information.

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/mingzilla/pi-api-mcp-server'

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