Skip to main content
Glama

set_project_context

DestructiveIdempotent

Set or replace compact project context. The encoded API request body is capped at 512KB. Read existing context first, merge still-valid entries, inspect event names with properties or properties_received, and save only durable product truth tied to goals, activation events, event-name glossary entries, or date annotations for major product changes. Use annotations for meaningful landing page, pricing, onboarding, feature, release, or experiment changes; do not store git commit logs, noisy edits, PII, secrets, or long release notes.

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": {
      "project": "<project>"
    },
    "name": "set_project_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalsNoShort business goals, max 5
projectYesProject name or ID
glossaryNoEvent-name glossary entries, max 10
annotationsNoMajor date annotations, max 100
activation_eventsNoEvent names that define activation, max 8

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description adds real context on top: a 512KB cap on the encoded request body, the replace-not-merge semantics implied by 'Read existing context first, merge still-valid entries', and content-policy constraints on what may be stored. It stops short of stating outright that anything not re-included is lost, which would be the most valuable explicit warning for a destructive 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?

Three dense sentences, front-loaded with the action and the size cap before the workflow and the content policy. The long clause list at the end is justified because each item is a distinct rule, though the sentence runs long and could be split for scannability.

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 five-parameter destructive write tool with no output schema, the description covers the main risks: size limit, replace semantics, read-before-write workflow, and what must not be stored. The only gap is success behavior — whether the call returns the stored context or just an acknowledgment — which matters less given there is no output schema.

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 coverage is 100% with per-field descriptions and max-item limits, so the baseline is 3; the description earns an extra point by mapping content policy onto specific parameters — goals and activation events as durable product truth, glossary entries as event-name definitions, and annotations as major landing page, pricing, onboarding, feature, release, or experiment changes. That distinguishes what belongs in `annotations` versus `glossary` in a way the schema's terse field descriptions do not.

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 opens with a specific verb and resource ('Set or replace compact project context'), and the 'replace' wording signals that the whole object is overwritten rather than patched. It does not explicitly name the sibling it competes with (get_project_context, append_project_annotation), leaving the agent to infer that this is the bulk-write counterpart to the read/append tools.

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

Usage Guidelines5/5

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

It gives an ordered workflow ('Read existing context first, merge still-valid entries, inspect event names with properties or properties_received') and names the sibling tools to use for event inspection. It also supplies an explicit inclusion list (goals, activation events, glossary, date annotations) and an exclusion list (git commit logs, noisy edits, PII, secrets, long release notes), so when-to-use and when-not-to-use are both unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources