Skip to main content
Glama
Sign In
Mimicus

Mimicus

by qwzx4893-stack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

mimicus_close_session

Close selected owned browser sessions and release contexts, proxies and analyses. Supply sessionId or a bounded sessionIds batch.

Instructions

Close selected owned browser sessions and release contexts, proxies and analyses. Supply sessionId or a bounded sessionIds 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_close_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdNo
sessionIdsNo

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, and the description is consistent with that profile. Beyond the annotations, it adds real value: it names the side effects (contexts, proxies and analyses are released) and constrains scope to sessions the caller owns, which is an ownership/permission signal annotations alone do not convey. It does not say whether closure is reversible or what happens to in-flight work.

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, zero waste. The action and its effects are front-loaded, and the parameter-form note follows as a compact second sentence.

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. Still, for a tear-down tool with 0 required parameters and no annotation coverage of failure behavior, the description should state whether exactly one of sessionId/sessionIds must be supplied and what happens on partial or invalid ids. Those gaps leave the agent to guess.

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 carries the burden, and it does clarify the intended either/or relationship between sessionId and sessionIds. However, it only hints at the batch bound ('bounded') without stating maxItems=4, and never says the two are mutually exclusive alternatives or that at least one is required despite the schema having zero required parameters.

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+resource ('Close selected owned browser sessions') and enumerates what gets released (contexts, proxies, analyses). This distinguishes it from every sibling tool, none of which tear down sessions. It falls short of 5 only because 'selected owned' leaves the selection criterion (ownership scoping) implicit.

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?

The second sentence gives some invocation guidance by naming the two calling forms, implying 'pick one of sessionId or sessionIds'. But there is no statement of when to close versus leaving sessions open, no prerequisites, and no exclusions. Usage is implied rather than specified.

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