Skip to main content
Glama

route_feature

Configures routing preferences for a feature, including worker type, capabilities, parallelism, and isolation level, so parallel coding workers run with the needed constraints.

Instructions

Configure routing for a feature. Sets preferences for worker type, capabilities, parallelism, and isolation level.

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": "route_feature"
  }
}

Input Schema

NameRequiredDescriptionDefault
featureIdYesID of the feature to configure routing for
projectDirYesAbsolute path to the project directory
affinityGroupNoGroup features that should run on the same worker
isolationLevelNoIsolation level for the worker
maxParallelismNoMaximum concurrent workers for this feature
excludeCapabilitiesNoCapabilities to avoid
preferredWorkerTypeNoHint for worker specialization (e.g., 'frontend', 'backend', 'testing')
requiredCapabilitiesNoCapabilities the worker must have

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 must carry the full behavioral burden. It says nothing about whether this replaces existing routing, whether it affects already-running workers, what defaults apply for omitted fields, or whether special permissions are needed—significant gaps for a configuration mutation tool.

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 purpose front-loaded and no filler. The second sentence is a compact enumeration of configurable dimensions, though it could be dropped since the schema already lists them.

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 an 8-parameter configuration tool with no annotations and no output schema, the description is thin. It does not say what happens on success, whether routing is persisted per feature, or how the settings interact with worker scheduling—information an agent needs before invoking it.

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 coverage is 100%, so each parameter's meaning and constraints (including the isolationLevel enum and maxParallelism bounds) are already documented. The description's list of routing dimensions adds only a light conceptual grouping over the schema and does not explain affinityGroup or excludeCapabilities beyond what the schema says.

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 uses a specific verb (Configure) and resource (routing for a feature), and lists the dimensions being set (worker type, capabilities, parallelism, isolation level). It does not distinguish this from siblings such as enqueue_feature or auto_orchestrate, so an agent must infer whether routing is a prerequisite or an alternative.

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 statement of when this tool should be used, what prerequisites exist (e.g., must the feature already exist?), or how it relates to enqueue_feature/auto_orchestrate. The agent is left to infer usage entirely from the name and field list.

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