Skip to main content
Glama
Sign In
ya-tracker-mcp

ya-tracker-mcp

by imdeniil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_component

Create a component in a specified queue, with optional lead login, auto-assign behavior, and description.

Instructions

Create a new component.

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": {
      "name": "<name>",
      "queue": "<queue>"
    },
    "name": "create_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
leadNoComponent lead login
nameYesComponent name
queueYesQueue key (e.g. "DEV")
assign_autoNoAuto-assign issues to lead
descriptionNoComponent description

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.2

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action 'Create a new component' without revealing any side effects, required permissions, or consequences. It does not mention whether the component is immediately visible, if creation can be undone, or any other behavioral traits beyond the bare verb.

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

Conciseness4/5

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

The description is a single, concise sentence that states the core purpose without any wasted words. It is appropriately sized for a simple creation tool, though it lacks any additional structured context (e.g., usage examples or note sections). It is not verbose, but it is also not maximally informative.

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 that there are 5 parameters, an output schema, and no annotations, the description is insufficiently complete. It does not provide any behavioral context, usage guidelines, or return value expectations. The existence of an output schema covers return values, but the description remains minimal and does not help the agent understand the full scope of the operation.

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% (all five parameters have descriptions in the schema). The tool description adds no additional parameter information, but per the rubric, a high schema coverage sets the baseline at 3. The description does not hinder understanding but also does not compensate for anything missing.

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?

The description 'Create a new component' uses a specific verb ('Create') and resource ('component'), clearly distinguishing it from sibling tools like update_component (which modifies) or list_components (which lists). The action is unambiguous and directly matches the tool name.

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. It does not mention prerequisites, typical scenarios, or any exclusions. Sibling tools such as update_component or list_components exist, but the description offers no comparison or context to help an agent choose correctly.

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