Skip to main content
Glama

A person's favourites

favorites
DestructiveIdempotent

Needs the person's access token. action: list, add or remove a favourite product or digital plan.

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": {
      "action": "<action>"
    },
    "name": "favorites"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoProduct slug or digital plan id
kindNoproduct or digital
limitNoMax rows
actionYesOperation to run; help {topic:"favorites"} lists each one's arguments
detailNocompact (default) or full
offsetNoRows to skip
countryNoCountry code, e.g. CZ

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / action / description
      Added value: +"Operation to run; help {topic:\"favorites\"} lists each one's arguments"
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "compact (default) or full",
      +  "enum": [
      +    "compact",
      +    "full"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Max rows",
      +  "type": "number"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Rows to skip",
      +  "type": "number"
      +}
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already disclose the safety profile (destructiveHint=true, idempotentHint=true, not read-only), so the bar is lower, and the description does add the genuine extra fact that a person's access token is required. It says nothing about what removal discards, whether add is idempotent per product, rate limits, or the shape of results, which are meaningful gaps for a destructive tool.

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?

Two short sentences with no filler, though leading with the access-token prerequisite rather than the core operation undercuts front-loading of purpose. The 'action:' phrasing is telegraphic but not wasteful.

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

Completeness3/5

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

With seven parameters, fully covered schema, and no output schema, the description is only minimally sufficient: it never sketches what a list returns or what add/remove return, and it defers argument details to the help tool. For a mutation-capable tool with destructiveHint=true, that is adequate but not thorough.

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%, so the schema already documents id, kind, limit, offset, detail, country, and action. The description only restates the action vocabulary and loosely maps id to 'product slug or digital plan id', adding little beyond structured data; it is silent on the interaction between kind and id and on pagination.

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 names a concrete resource (favourite product or digital plan) and the concrete operations (list, add, remove), so the agent knows exactly what the tool does. It does not, however, contrast itself with near neighbours such as digital, product, or lists, so sibling differentiation is left to inference.

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 only usage context given is the access-token prerequisite plus the available actions, which implies when each action applies (read vs. mutate). There is no explicit guidance on when to prefer this over related tools like lists or product, and no exclusions or preconditions beyond auth.

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