Skip to main content
Glama

set_project_category

Assign or change a project's category label to organize it with related work on the dashboard. Retrieve existing categories with get_project_categories to avoid duplicates.

Instructions

Assign or change a project's category.

Sets the grouping label on a project so it sorts with related work on the
dashboard. Call get_project_categories first to reuse an existing label
rather than creating a near-duplicate.

Args:
    project_id: The project_id of the project to update.
    category: The category label to assign (e.g. "Article", "Grant");
        surrounding whitespace is trimmed.

Returns:
    A confirmation message naming the category and project that were set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
categoryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses that the category label is assigned or changed, whitespace is trimmed, and returns a confirmation message. Lacks mention of error conditions or permissions, but overall informative.

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?

Concise, well-structured with separate paragraphs for purpose, usage, args, and returns. No redundant information.

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

Completeness5/5

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

Complete for a simple two-parameter tool with output schema; covers purpose, parameters, return, and usage context adequately.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds full semantic context for both parameters: project_id and category, with examples and trimming behavior. Compensates for 0% schema description coverage.

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?

Clearly states the verb 'assign or change' and the resource 'project's category'. Differentiates from sibling tools like get_project_categories and create_project by specifying its unique action.

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

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs to call get_project_categories first to reuse existing labels, preventing duplicates. Provides clear when-to-use and when-not-to guidance.

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/SVerITG/Metis_PH'

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