Skip to main content
Glama

Update Context

update_context

Update a specific field in the project context using dot notation to keep project metadata and conventions current without rewriting the whole context.

Instructions

Update a specific field in the project context using dot notation (e.g. 'project.description', 'conventions.code_style').

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": {
      "dot_path": "<dot_path>",
      "value": "<value>"
    },
    "name": "update_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoProject root directory..
valueYesThe value to set.
dot_pathYesDot-notation path to the field (e.g. 'project.description').

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/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 behavioral burden for a mutation tool. It does not say whether the value overwrites, what happens if the dot path does not yet exist, whether invalid paths error out, or whether the change is reversible.

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

Conciseness5/5

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

A single sentence with the mechanism and examples front-loaded; no filler, no restating the title.

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

Completeness4/5

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

An output schema exists so return values needn't be described, and the parameters are fully covered by the schema. What remains missing is mutation behavior and path validity, which is a modest but real gap for a write 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 the baseline is 3; the schema already explains dot_path, value, and path. The description's dot-notation examples restate the schema's own example without adding new meaning, such as which top-level context keys are valid.

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 ('Update a specific field in the project context') plus the addressing mechanism (dot notation) with two concrete path examples. An agent can distinguish it from get_context or update_prd, though no sibling is named explicitly.

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 dot-notation examples imply how to call it, but there is no explicit when-to-use guidance, no mention of prerequisites (e.g. whether init_context must run first), and no routing between this and siblings like add_to_context_list or update_prd that also mutate project state.

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