Skip to main content
Glama
Sign In
Mimicus

Mimicus

by qwzx4893-stack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

mimicus_end_discovery

Release selected temporary discovery operations and their candidates/cursors. Supply operationId or a bounded operationIds batch.

Instructions

Release selected temporary discovery operations and their candidates/cursors. Supply operationId or a bounded operationIds batch.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mimicus_end_discovery"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationIdNo
operationIdsNo

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.0
    • addedInput schema / properties / operationIds
      Added value: +{
+  "items": {
+    "maxLength": 100,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 20,
+  "minItems": 1,
+  "type": "array"
+}
    • removedInput schema / required
      Removed value: -[
-  "operationId"
-]
  2. First observedv0.3.0-beta.2

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true). The description adds useful specifics about what is released (temporary discovery operations and their candidates/cursors), but does not explain reversibility, auth requirements, or error behavior.

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 sentences, front-loaded with the action and followed by the parameter requirement. There is no redundant or filler text.

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?

An output schema exists, so return values need not be described. For a simple two-parameter cleanup tool the description covers the core action and invocation pattern, but the low schema coverage means more parameter detail (batch limit, mutual exclusivity) would be needed for full completeness.

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?

Schema description coverage is 0%, so the description must carry parameter meaning. It does explain that operationId or a bounded operationIds batch should be supplied and implies mutual exclusivity, but omits concrete limits such as the schema's maxItems of 20 and does not clarify that neither parameter is marked required.

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 states a specific verb ('Release') and resource ('temporary discovery operations and their candidates/cursors'), so an agent knows exactly what the tool acts on. It does not explicitly distinguish this cleanup operation from siblings such as mimicus_close_session, keeping it below a 5.

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?

Usage is implied by 'selected temporary discovery operations' and by the invocation instruction to supply an ID or batch, but there is no explicit when-to-use versus when-not-to-use guidance or comparison to alternatives like mimicus_close_session.

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