Skip to main content
Glama
Sign In
DevRev MCP Server

DevRev MCP Server

Official
by devrev
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Python

create_part

Create a new enhancement in DevRev by specifying type, name, assigned users, parent parts, and description.

Instructions

Create a new part (enhancement) in DevRev

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": {
      "type": "<type>",
      "name": "<name>",
      "owned_by": "<owned_by>",
      "parent_part": "<parent_part>"
    },
    "name": "create_part"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes
nameYes
owned_byYesThe DevRev IDs of the users assigned to the part
parent_partYesThe DevRev IDs of the parent parts
descriptionNoThe description of the part

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
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 mentions creation but lacks details on permissions needed, whether it's idempotent, error handling, or what happens on success/failure. For a mutation tool, this is a significant gap in transparency.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy for an agent to parse quickly.

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?

For a creation tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It lacks behavioral context, usage guidelines, and details on return values or side effects, which are critical for an agent to invoke it correctly.

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 60%, with descriptions for 'owned_by', 'parent_part', and 'description'. The tool description adds no parameter semantics beyond the schema, but the baseline is 3 since schema coverage is moderate and the description doesn't compensate or contradict.

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 action ('Create') and resource ('new part (enhancement) in DevRev'), making the purpose unambiguous. It doesn't explicitly differentiate from siblings like 'create_work' or 'update_part', but the specificity of 'part (enhancement)' provides some implicit distinction.

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 like 'create_work' or 'update_part'. The description states what it does but offers no context about prerequisites, appropriate scenarios, or exclusions, leaving the agent to infer usage.

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