Skip to main content
Glama
Sign In
HacknPlan MCP

HacknPlan MCP

by jompereira
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

create_project_role

Create a new role for a project by providing name and description. Define permissions to organize team members effectively.

Instructions

Create a new role in a project

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": {
      "projectId": "<projectId>",
      "name": "<name>"
    },
    "name": "create_project_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
projectIdYes
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations exist, and the description omits behavioral details such as whether duplicate names are allowed, required permissions, or if the created role is returned. It only states the basic action.

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 a single sentence, concise but under-specified. It could include more critical info without becoming verbose.

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 the simple tool and no output schema, the description lacks context about expected return value, required permissions, or behavior on error. Insufficient for an agent to fully understand the tool's use.

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

Parameters1/5

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

With 0% schema description coverage, the description should add meaning but does not: it mentions no parameter details beyond the schema's property names, lacking explanation of 'name', 'projectId', or 'description'.

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 'Create a new role in a project' clearly states the action (create) and the resource (project role), but does not explicitly differentiate from siblings like 'replace_project_role' or 'update_project_role', though the name implies creation.

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 guidance is provided on when to use this tool versus alternatives (e.g., update_project_role for modifications) or any prerequisites like project existence.

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