Skip to main content
Glama

Reopen a pick link for another browser

reopen_shop_window
DestructiveIdempotent

Reopen a pick link you made with show_shop_to_owner (its window_id) for another browser: after your human opened it on one device or app, it opens only there. This frees it, so it opens in the next browser where they press Open my page; the link and the picks stay. Use it only when your human asks (for example "it says open in another browser"), then send the same pick_url again, only to them, in a private message. At most 5 times a day per link (then shop_window_reopen_limit). A closed or expired link cannot be reopened (close_shop_window ends one for good): make a new one. 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": "reopen_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.8/5.0
Behavior5/5

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

Beyond the annotations, it discloses a hard quota ("At most 5 times a day per link", plus the shop_window_reopen_limit error), authorization scope ("Only the passport that made it"), failure conditions (closed or expired links cannot be reopened), and state effects ("the link and the picks stay", the binding is freed). These details explain the destructiveHint=true annotation rather than contradicting it — the mutation is the release of the browser binding.

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 most important constraint (this is a deliberate, user-requested action) is front-loaded, and every clause carries operational information — quota, idempotency of the link, auth scope. It is dense and runs long as a single block, which slightly hurts scanability, but nothing is filler.

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 mutation with no output schema, the description covers the source of the id, the authorization requirement, the rate limit and its error, the unrecoverable states, and the exact next action toward the human. Nothing an agent needs to call this correctly or recover from failure is missing.

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 baseline is 3; the description adds meaning by explaining that window_id comes from show_shop_to_owner and that the same pick_url must be resent to the user afterwards, which clarifies the intended workflow rather than just the field type. The passport_token fallback is left entirely to the schema, so it is not a full 5.

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 opens with a specific verb+resource ("Reopen a pick link") and traces the object back to the sibling that creates it ("you made with show_shop_to_owner (its window_id)"). It also names the contrasting sibling close_shop_window, so an agent can distinguish reopening from closing without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit trigger condition ("Use it only when your human asks") with a concrete example utterance, names the alternative path for dead links (close_shop_window / make a new one), and prescribes the follow-up action (resend the same pick_url privately). When-to-use, when-not-to-use, and the downstream step are all stated.

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.