Skip to main content
Glama

close_cards

Close cards created with show_card to clear them from the specified browser tab.

Instructions

Close the cards you put on the page with show_card.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tabId": "<tabId>"
    },
    "name": "close_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdYesTab ID, from tabs_list or tab_create

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does reveal the important scope fact that only cards created via show_card are affected, which bounds the destruction, but it omits whether the close is reversible, what the response looks like, whether tabId must match the creating tab, and what happens on error or when no cards exist.

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 short sentence, front-loaded with the action and resource, with zero filler. The embedded reference to show_card is the only extra clause and it earns its place by establishing the pairing.

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 one-parameter, annotation-free, output-schema-free cleanup tool this is close to sufficient: the agent knows the action, the target resource, and which prior tool created it. Adding the no-cards/error behavior and the fact that the tabId should be the same tab used for show_card would make it fully self-contained.

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 100% for the single tabId parameter, and the schema even points at tabs_list/tab_create as sources for the value. The description adds nothing about tabId, so the baseline 3 for fully documented parameters 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?

Specific verb ('Close') plus a concrete resource ('the cards you put on the page'), and it ties itself directly to the sibling show_card, so the pairing is unambiguous. It stops short of differentiating from tab_close or clear_annotations by name, but the resource noun 'cards' is distinctive enough for an agent to select it correctly.

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?

Usage is implied through the show_card reference: put cards on the page, then close them. There is no explicit when-to-use/when-not statement, no mention of what happens if no cards are open, and no guidance separating it from tab_close or clear_annotations, so an agent must infer these boundaries.

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