Skip to main content
Glama

breely_close

Closes the active browser session when work is complete, stopping credit consumption. Use it to end the session and prevent unused credits from continuing to run.

Instructions

Close the Breely 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": "breely_close"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral burden, and it does disclose the cost consequence of leaving the session open, which is genuinely useful. It does not say whether closing discards browser state, whether the call is idempotent if no session is open, or what happens to in-progress work, so the operational picture is only partly covered.

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 reason attached as a trailing clause; there is no filler and no sentence that fails to earn its place.

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 zero-parameter, no-output session-termination tool, the description covers what it does, when, and why. The only real gap is the state-loss and idempotency behavior, which matters for an agent deciding whether it is safe to call mid-task.

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 no parameters and the schema is closed with additionalProperties false, so there is no parameter meaning to explain. Baseline 4 applies since nothing about invocation inputs is left ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Close the Breely browser session') plus the outcome it produces ('credits stop running'), which is enough for an agent to distinguish it from the other breely_* action tools such as open, read, or status.

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?

It gives an explicit trigger condition, 'when the work is done', so an agent knows the moment to call it rather than guessing. There is no when-not guidance or named alternative, but no sibling performs a competing close action, so the practical gap is small.

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