Skip to main content
Glama

A person's saved comparisons

comparisons
Destructive

Needs the person's access token. action: list, save (2-4 plans), share (by link) or delete a saved comparison of digital plans.

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": "comparisons"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName
itemsNo2-4 plan ids (save)
limitNoMax rows
actionYesOperation to run; help {topic:"comparisons"} lists each one's arguments
detailNocompact (default) or full
localeNoLanguage, e.g. cs
offsetNoRows to skip
sharedNoShare by link
comparison_idNoComparison id

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:\"comparisons\"} 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 declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false; the description's mention of a delete action is consistent with that. It usefully adds the access-token prerequisite, but doesn't state what delete removes irrevocably or what share exposes publicly.

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, front-loaded with the auth prerequisite and then the action enumeration, with essentially no wasted words. The telegraphic style is terse but parseable.

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?

For a nine-parameter tool with a destructive operation and no output schema, the description covers auth and action routing but leaves the consequences of delete and the shape of list results unexplained. Adequate but with clear gaps.

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 all nine parameters are already documented in the schema, establishing a baseline of 3. The description only echoes two of them (items = 2-4 plans, shared = by link) without adding format or constraint detail beyond the schema.

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 the resource (a person's saved comparisons of digital plans) and enumerates the four supported operations: list, save, share, delete. This is specific enough to distinguish it from siblings like product or lists, though it doesn't explicitly contrast with them.

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?

It gives partial routing guidance: save requires 2-4 plans, share is by link, and an access token is required. However, it never says when to prefer this over related tools such as product, favorites, or lists, and it offers no when-not guidance.

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