Skip to main content
Glama

get_feature_complexity

Analyze a feature's complexity and get a recommendation on whether competitive planning is needed.

Instructions

Analyze the complexity of a feature and get a recommendation for whether to use competitive planning.

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": {
      "projectDir": "<projectDir>",
      "featureId": "<featureId>"
    },
    "name": "get_feature_complexity"
  }
}

Input Schema

NameRequiredDescriptionDefault
featureIdYesID of the feature to analyze
thresholdNoComplexity threshold for competitive planning (default: 60)
projectDirYesAbsolute path to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does not say whether analysis is read-only (implied but unstated), whether it writes any state, how expensive it is, or what the recommendation actually contains (a score? a boolean? a message?). For a zero-annotation tool this is a meaningful gap.

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?

A single, front-loaded sentence with no filler or repetition. It is efficient, though its brevity borders on under-specification rather than optimal density.

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

Completeness3/5

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

With three well-documented parameters and no output schema, the definition covers the inputs adequately but leaves the return value and the threshold semantics unexplained. For a decision-support tool whose whole purpose is producing a recommendation, the output side deserves at least a sentence.

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%, so all three parameters (featureId, projectDir, threshold with its default of 60) are already documented in the schema. The description adds no further meaning about how the threshold influences the recommendation, so the baseline 3 applies.

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 names a specific verb ('Analyze') and resource ('complexity of a feature') and states the output ('a recommendation for whether to use competitive planning'). No sibling in the list performs complexity analysis, so the tool's role is distinguishable even without an explicit 'unlike X' clause.

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

Usage Guidelines3/5

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

The purpose implies a use case — run this before deciding whether competitive planning is warranted — but there is no explicit when-to-use/when-not guidance, no stated prerequisites (e.g., must the feature already exist or be enriched?), and no named alternative for related planning decisions.

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