Skip to main content
Glama

Airsockfly

Save or unsave offer

toggle_saved_offer

Save an offer to the user's favourites, or remove it when it is already saved.

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": {
      "vertical": "<vertical>",
      "externalId": "<externalId>"
    },
    "name": "toggle_saved_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
verticalYesService type.
externalIdYesOffer identifier (externalId) returned by a search tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare this as a non-read-only, non-destructive, non-idempotent mutation. The description adds the key behavior beyond that: a single call both adds and removes depending on current state, which explains the state-dependent (non-idempotent) nature. It omits whether removal fails when the offer is not saved, and any auth/user-scoping requirement.

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?

A single sentence with zero filler, and the primary action (save) is front-loaded ahead of the reverse case. Slightly terse for a toggle tool, but nothing is wasted.

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 simple two-parameter mutation with full schema coverage and no output schema, the description covers the essential action and its dual direction. It does not state what the call returns (the resulting saved state) or the error case when unsaving a non-saved offer, which is a minor remaining gap.

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%: vertical's enum and externalId's origin ('returned by a search tool') are already documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline 3 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 gives a specific verb pair (save/remove) and resource (offer, user's favourites), making the toggle semantics unmistakable. It does not name a sibling such as list_saved_offers or get_offer to distinguish when to check state first, so it stops short of a 5.

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?

The phrase 'or remove it when it is already saved' implies the caller need not know the current saved state before calling, which is useful usage guidance. However, there is no explicit statement of when to prefer this over list_saved_offers, nor any precondition or exclusion.

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.

Resources