Skip to main content
Glama

get_feature_graph

Retrieve the feature dependency graph with context summaries and protocol bindings to understand feature relationships and dependencies in a project.

Instructions

Get the feature dependency graph with context information. Shows relationships between features, their dependencies, and enriched context summaries.

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>"
    },
    "name": "get_feature_graph"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoOutput format (default: pretty)
projectDirYesAbsolute path to the project directory
includeContextNoInclude context summaries (default: true)
includeProtocolsNoInclude protocol bindings (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. 'Get' implies a read, but it never confirms the operation is side-effect free, says nothing about graph size or cost on large projects, and gives no sense of the returned structure beyond a one-line summary.

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?

Two short sentences with the core purpose front-loaded. The second sentence largely restates the first with slightly more detail, so it earns its place only marginally, but there is no bloat.

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 no annotations and no output schema, the description should say more about what a caller receives. Naming dependencies, relationships, and context summaries helps, but the shape, size, and cost of the graph remain unexplained for a four-parameter query tool.

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 four parameters are already documented, and the description adds only a loose connection between 'context summaries' and includeContext. It says nothing about the format enum values (compact/pretty/json) or what protocol bindings are.

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?

States a specific verb and resource: 'Get the feature dependency graph with context information.' That clearly distinguishes it from siblings like get_feature_complexity or get_base_constraints without needing to name them, though it doesn't explicitly position itself against them.

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?

There is no when-to-use guidance, no statement of prerequisites, and no exclusions or alternatives. An agent must infer usage from the name alone; nothing tells it whether this is the right call when it also needs complexity or constraint data.

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