Skip to main content
Glama

Close a pick link

close_shop_window
DestructiveIdempotent

Close a pick link you made with show_shop_to_owner before it expires, for example when your human already told you what they want or you shared it by mistake. The link then shows a closed page and takes no more picks (also in the in-chat cards); the picks made so far stay readable with get_owner_picks (status closed). Closing again changes nothing, and it cannot be reopened (reopen_shop_window moves an open link to another browser). Only the passport that made it.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "window_id": "shw_exampleshopwindowaaaaa"
    },
    "name": "close_shop_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
window_idYesid from show_shop_to_owner (shw_...).
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "window_id": "shw_exampleshopwindowaaaaa"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=true, but the description adds what those mean in practice: the link shows a closed page, accepts no more picks including in-chat cards, existing picks stay readable via get_owner_picks (status closed), repeat calls are no-ops, and the action is irreversible. It also states an ownership constraint ('Only the passport that made it'), which is exactly the kind of auth context annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action and its effect are front-loaded, and every clause carries real information (result state, card behavior, data survival, idempotency, irreversibility, auth). It is a single long run-on sentence with stacked parentheticals, which costs a little readability but wastes no words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, no-output-schema mutation tool, the description covers the outcome state, what survives, idempotency, irreversibility, and the ownership requirement. Nothing an agent needs in order to decide or call correctly is absent.

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?

Schema coverage is 100%, so the baseline is 3, and the description adds an authorization qualifier on passport_token ('Only the passport that made it') that the schema does not state. It does not elaborate on the window_id format, but the schema already covers that.

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 uses a specific verb ('Close') on a specific resource ('a pick link you made with show_shop_to_owner') and states the scope ('before it expires'). It also explicitly separates this tool from reopen_shop_window and points to get_owner_picks for the surviving data, so an agent can distinguish it from its siblings without opening any schema.

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 concrete when-to-use triggers ('your human already told you what they want or you shared it by mistake') and names the alternative reopen_shop_window, clarifying that it does not reopen. What is missing is an explicit warning not to close a link you might still need, which is only implied by 'cannot be reopened'.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.