Skip to main content
Glama

Clear my repository override

clear_repo_override
DestructiveIdempotent

Delete your own repository override, reverting to repository and inherited settings. Any workspace member; no effect on other members.

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": {
      "workspace_id": "<workspace_id>",
      "repo_id": "<repo_id>"
    },
    "name": "clear_repo_override"
  }
}

Input Schema

NameRequiredDescriptionDefault
repo_idYesThe repository id from get_workspace.
workspace_idYesThe workspace id (from whoami).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is structured. The description adds value beyond that by explaining what the deletion actually does (falls back to repository and inherited settings) and that blast radius is limited to the caller's own override, which the annotations alone do not convey.

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 filler: the action and its effect come first, followed by the permission and blast-radius caveat. Every clause carries distinct information.

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

Completeness5/5

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

For a two-parameter, no-output-schema mutation, the description covers action, resulting state, who may invoke it, and scope of impact, while annotations supply the destructive/idempotent profile. Nothing material is missing for correct invocation.

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?

Both parameters are fully documented in the schema at 100% coverage, including provenance hints (repo_id from get_workspace, workspace_id from whoami). The description adds no further meaning such as format, ownership constraints, or error conditions per parameter, so the baseline 3 applies.

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 pairs a specific verb ("Delete") with a specific resource ("your own repository override") and states the resulting state (reverting to repository and inherited settings). The "your own" scoping distinguishes it from any operation on other members' overrides, though it never names set_repo_override as the counterpart it undoes.

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

Usage Guidelines3/5

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

"Any workspace member; no effect on other members" gives permission and scope but not an explicit when-to-use condition or a named alternative. The intended usage is inferable from the revert semantics, and the sibling set_repo_override is implied but never referenced, so guidance is adequate rather than explicit.

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