Skip to main content
Glama

tumblr_close

Ends the Tumblr browser session once your work is finished, so session credits stop running. Use it to release the connection and avoid continued usage charges.

Instructions

Close the Tumblr 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": "tumblr_close"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does add genuine value by naming the consequence, 'credits stop running,' which explains why the tool exists and what state change results. However, it says nothing about idempotency, whether an error occurs if no session is open, or whether any session data is lost on close.

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 motivation trailing. Every clause earns its place: what to do, when to do it, and why it matters.

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-teardown tool with no output schema, the description covers purpose, timing, and cost rationale, which is most of what an agent needs. The only missing piece is failure behavior when there is no active session to close.

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?

The tool takes zero parameters, so there is no parameter meaning to add and the baseline is 4. The description offers no additional invocation detail beyond the trigger condition, which is acceptable for a no-arg tool but adds nothing on this dimension.

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 uses a specific verb and resource: 'Close the Tumblr browser session.' It is clearly the counterpart to the tumblr_open sibling, though it never names that sibling or explicitly frames itself as the teardown step, so differentiation is inferred rather than stated.

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 calling the tool. It stops short of a full when/when-not rule set (e.g., behavior if no session is open, or whether to call before or after tumblr_read completes), so it is clear context but not complete routing guidance.

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