Skip to main content
Glama

monograph_close

Close the Monograph browser session when work is complete to stop credit usage.

Instructions

Close the Monograph browser session when the work is done, so credits stop running.

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": "monograph_close"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden. It does well to state the consequence — credits stop running — which is useful behavioral context beyond the name. However, it does not say whether unsaved work is lost, whether the session can be resumed, whether the call is idempotent if no session is open, or what is returned.

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?

A single sentence with the action front-loaded and the rationale (credits) trailing as supporting justification. No filler, no restatement of the tool name beyond what is needed, and nothing to trim.

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 no-parameter, no-output, no-annotation teardown tool, the description covers purpose, timing, and the practical cost of not calling it. The only real gap is failure/idempotency behavior — what happens when no session exists — which is minor at this complexity level.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The input schema is empty with additionalProperties false, matching the absence of any parameter discussion in the description.

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 names a specific verb and resource — "Close the Monograph browser session" — which is unambiguous and clearly distinct from the read/click/type/open siblings. It stops just short of explicitly naming a counterpart tool (e.g., open), so it gets a 4 rather than 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 Guidelines4/5

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

"When the work is done" gives a concrete trigger condition for invoking the tool, which is the key usage decision for a session-terminating call. There is no explicit when-not guidance or named alternative, but for a zero-parameter teardown tool the timing hint is sufficient context.

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