Skip to main content
Glama

dribbble_close

Close the active Dribbble browser session after completing work to stop credits from running. End the session to prevent unnecessary credit consumption.

Instructions

Close the Dribbble 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": "dribbble_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 supplied, the description carries the full behavioral burden. It discloses the meaningful side effect, that the session terminates and metered credits stop accruing, which is genuinely useful context. It does not say whether the call is idempotent, what happens if no session is open, or whether any work state is lost, so gaps remain for a session-terminating operation.

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?

One sentence, front-loaded with the action and followed by the reason to invoke it. Every clause earns its place and nothing is padded.

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 session-closing tool with no output schema, the description covers what it does and why an agent should call it. Only edge-case behavior, such as calling it with no active session, is left unstated, which is a minor omission at this simplicity 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 and the schema is empty, so there is no parameter meaning the description could add. The baseline for a no-parameter tool applies.

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 pairs a specific verb ("Close") with a specific resource ("the Dribbble browser session") and even states the consequence ("credits stop running"). It is unambiguous what the tool acts on, though it does not explicitly contrast itself with siblings like dribbble_open or dribbble_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 a clear trigger condition: call this "when the work is done." That is actionable guidance for an agent sequencing the other dribbble_* tools, but there is no stated exclusion (e.g., what to do if no session exists) or mention of any alternative tool.

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