Skip to main content
Glama

publish_context

Publish or update key-value metadata on the shared project board so all agents can access goals, milestones, constraints, and environment variables.

Instructions

Publishes or updates a key-value pair on the living project board.

Call this tool to record persistent high-level metadata that all agents need to see, such as project goals, active milestones, or shared environment variables.

Standard Keys:

  • 'goal': The primary objective of the repository/project.

  • 'current_milestone': The current phase or sprint objective (e.g., 'Phase 4: FastMCP').

  • 'constraints': Line-delimited or bulleted technical invariants.

Args: key: The configuration or metadata key (e.g., 'current_milestone', 'constraints'). value: The string value to store. If storing constraints, use newline-separated bullet points with exact technical parameters.

Returns: str: Confirmation message acknowledging the stored key-value pair.

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": {
      "key": "<key>",
      "value": "<value>"
    },
    "name": "publish_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
valueYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior3/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 discloses useful context — that values persist and are visible to all agents, and what the confirmation return looks like — but it never states whether writing an existing key overwrites the prior value, whether there are size or concurrency limits, or what permissions are required for a shared board. For a mutation tool with zero annotation coverage these are meaningful gaps.

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?

Front-loaded with the action sentence, then a usage trigger, then an enumerated standard-key block, then Args/Returns. Structure is easy to scan. Minor waste: the 'Returns' section restates the output schema, and the Args block largely repeats the Standard Keys list already given above.

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?

For a two-required-parameter write tool with an output schema (so return values need no explanation) and no annotations, the description covers purpose, triggers, key vocabulary, and value formatting. The remaining gap is mutation semantics — overwrite behavior and any limits on shared metadata — which is the one thing an agent could get wrong when calling this repeatedly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must supply all parameter meaning, and it does: 'key' is illustrated with example keys and a documented 'Standard Keys' vocabulary, and 'value' gains formatting guidance ('newline-separated bullet points with exact technical parameters' for constraints). This goes well beyond the bare string types in the schema, though it doesn't say whether unknown/custom keys are allowed or how conflicts with standard keys are handled.

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 first sentence states a specific verb+resource ('Publishes or updates a key-value pair on the living project board'), which is far more than a restatement of the name. It implicitly distinguishes itself from the read-side siblings (get_project_board, get_recent_context) by framing the operation as writing persistent metadata, though it never names an alternative explicitly.

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

Usage Guidelines4/5

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

'Call this tool to record persistent high-level metadata that all agents need to see' plus concrete content examples (goals, milestones, environment variables) gives a clear trigger condition. It stops short of stating when NOT to use it — e.g., transactional notes versus decisions, which would route to record_decision — so a 4 rather than a 5.

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