Skip to main content
Glama

set_feature_context

Configure a feature's context by adding documentation references, prepared context blocks, and protocol bindings, with optional merging into existing context.

Instructions

Manually set context for a feature. Allows adding documentation references, prepared context blocks, and protocol bindings.

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

Input Schema

NameRequiredDescriptionDefault
mergeNoMerge with existing context instead of replacing (default: true)
preparedNoPre-processed context blocks
featureIdYesID of the feature to configure
projectDirYesAbsolute path to the project directory
documentationNoDocumentation references to add
protocolBindingsNoProtocol bindings to apply

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 disclosure burden and largely drops it. It never says what happens to pre-existing context, that the operation is a mutation, that merge defaults to true, or what validation errors look like; the merge default is only visible in the schema, not the prose.

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, front-loaded with the core action and followed by the accepted payload categories. There is no filler, though the second sentence is essentially a restatement of the parameter names.

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?

This is a mutation tool with six parameters, three of them arrays of structured objects, and it has neither annotations nor an output schema to lean on. Two sentences of prose cannot cover the replacement-vs-merge consequences, the meaning of the protocol binding scopes, or what the caller gets back.

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 the schema already explains merge, priority, scope, and the rest in detail. The description's naming of documentation references, prepared context blocks, and protocol bindings adds a light orientation layer but no semantics beyond the schema.

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 gives a specific verb+resource ('Manually set context for a feature') and enumerates the three content categories the tool accepts, which maps cleanly onto the documentation/prepared/protocolBindings parameters. It stops short of distinguishing itself from siblings such as enrich_feature or add_feature, though the word 'Manually' hints at the contrast.

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?

'Manually' implies this is the explicit, operator-driven path as opposed to automatic enrichment, which is a usable but indirect usage signal. There is no statement of when to prefer it over enrich_feature, no prerequisites, and no conditions under which it should not be called.

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