Skip to main content
Glama

SourceGeek

Save workspace context entry

upsert_workspace_context
Destructive

Create or update one workspace context entry (key, title, markdown content). Updating an existing key replaces its title and content. Workspace admins only; manual entries survive the daily auto-refresh.

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>",
      "title": "<title>",
      "content": "<content>"
    },
    "name": "upsert_workspace_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesKebab-case entry key. Reuse an existing key to update it.
titleYesShort human-readable title.
contentYesThe entry's markdown content.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the destructiveHint=true annotation, the description spells out exactly what destruction means: an existing key's title and content are wholesale replaced, not merged. It also discloses an authorization constraint (admins only) and a persistence trait (manual entries survive the daily auto-refresh), which the annotations do not cover. It omits the response shape, but the behavioral burden is largely met.

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?

Three tight sentences with no filler: capability first, update semantics second, constraints third. Every clause carries operative information, and nothing is buried behind preamble.

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?

With three required parameters, full schema coverage, and no output schema, the description covers the essentials an agent needs: what it writes, overwrite behavior, admin gating, and durability against auto-refresh. The only gap is that it says nothing about what a successful call returns or whether the entry is readable back via get_workspace_context, which is minor given the sibling exists.

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%, so the schema already defines all three parameters and even the kebab-case pattern. The description still adds meaning the schema does not: reusing a key performs a full replace of title and content rather than a partial patch, which shapes how an agent must populate the fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb pair and resource: 'Create or update one workspace context entry (key, title, markdown content).' It immediately distinguishes this upsert from the read/delete/list siblings by naming the exact artifact being written and the fields involved.

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?

It gives a hard prerequisite ('Workspace admins only') and clarifies the update path ('Updating an existing key replaces its title and content'), which tells an agent when this tool applies rather than a sibling. It stops short of naming an explicit alternative or exclusion, so it is clear context without full routing guidance.

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