Skip to main content
Glama
Sign In
Copilot Counterpart

Copilot Counterpart

by dstkwll
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

copilot_forget

Discards a completed, cleaned-up job from bridge memory without deleting SDK session files. Use it to remove job records while keeping routed request IDs reserved for the current process.

Instructions

Discard a finished, cleaned-up job from bridge memory. SDK session files are not deleted. Explicit-start deduplication is removed; routed request IDs remain reserved for this process and cannot be reused.

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": {
      "jobId": "<jobId>"
    },
    "name": "copilot_forget"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses that SDK session files are not deleted, that explicit-start deduplication is removed, and that routed request IDs stay reserved for the process. It omits idempotency and error behavior for ineligible jobs, but the side-effect profile is unusually well disclosed.

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 short sentences, front-loaded with the action and scope, then side effects. Every clause carries information; the 'explicit-start deduplication' and 'routed request IDs' phrasing is dense but purposeful.

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

Completeness3/5

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

For a single-parameter lifecycle tool with no annotations and no output schema, the description covers the memory/deduplication semantics well but leaves the parameter meaning and failure conditions unexplained. It is adequate, not complete.

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

Parameters2/5

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

Schema description coverage is 0% for the single required jobId parameter, so the schema supplies only a UUID format and no semantic meaning. The description never mentions jobId, so an agent gets no help on which identifier to supply or whether it must be a job this session created.

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 ('Discard a finished, cleaned-up job from bridge memory') plus the precondition that the job be finished and cleaned up, which implicitly separates it from cancel-style siblings. It does not name a sibling alternative outright, so differentiation is inferred rather than explicit.

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?

'Finished, cleaned-up job' implies the eligible state, but there is no explicit when-not guidance, no mention of what happens if the job is still running, and no routing to copilot_cancel or copilot_jobs for other lifecycle stages. Usage is implied rather than stated.

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

Deploy Server

Other Tools