Skip to main content
Glama

SourceGeek

Delete workspace context entry

delete_workspace_context
Destructive

Delete one workspace context entry by key. Workspace admins only; auto-refreshed entries come back on the next daily 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>"
    },
    "name": "delete_workspace_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe entry key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is structured data rather than description value. What the description does add is genuinely useful: the admin-only authorization requirement and the caveat that deletion of auto-refreshed entries is temporary. It says nothing about behavior when the key is absent or whether the call is idempotent, leaving meaningful gaps for a destructive operation.

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?

Two short sentences with no waste, front-loading the verb and resource, then the two operational caveats. Every clause carries information an agent could act on.

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 single-parameter destructive tool with full annotation coverage, the description supplies the two things the schema and annotations cannot: authorization scope and deletion durability. Only minor gaps remain (not-found behavior, idempotency), which are low-impact for correct selection.

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?

With one parameter at 100% schema description coverage, the schema already documents "key" fully with type and length bounds. The description's "by key" restates rather than adds semantics such as key format or uniqueness. Baseline 3 applies since the schema does the work.

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 ("Delete one workspace context entry by key") with singular scope, which distinguishes it operationally from upsert_workspace_context and get/list siblings. It stops short of naming an alternative explicitly, so it is clear but not maximally differentiating.

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?

Gives an explicit prerequisite ("Workspace admins only") and a condition under which deletion will not stick ("auto-refreshed entries come back on the next daily refresh"). It does not name an alternative tool or state when not to use this one, so it is strong 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