Skip to main content
Glama
Sign In
project-manager

project-manager

by samrullo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

pm_create_user_label

Create a user label by providing a name and optional user ID for project management.

Instructions

POST /user-labels — UserLabelCreate {name}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "payload": "<payload>"
    },
    "name": "pm_create_user_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes
x_user_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations, the description should disclose side effects, permissions, or idempotency. It only states the action without any behavioral details, such as whether the creation is immediate or requires confirmation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (one line), which is efficient, but it lacks structure and fails to provide essential information. It could be considered under-specified rather than properly concise.

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

Completeness1/5

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

Given the complexity of the nested payload parameter and the lack of schema descriptions and annotations, the description is wholly inadequate. It does not explain the return value, error conditions, or label usage semantics.

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

Parameters2/5

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

The description mentions {name} but does not clarify which parameter it corresponds to. The input schema has a payload object with additionalProperties, so the description adds nearly no meaning beyond the schema structure.

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 specifies the HTTP method (POST), endpoint (/user-labels), and action (Create), clearly indicating a resource creation operation. It distinguishes from sibling tools like pm_list_user_labels and pm_delete_user_label.

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 such as pm_user_attach_label or pm_create_tag. No context on prerequisites or typical use cases is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools