Skip to main content
Glama

recommend_across_lists

Cross-list recommendation: pulls candidates from every published Top 11 list, ranked by relevance to the problem. Use when the user's problem could span multiple categories.

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": {
      "problem": "<problem>"
    },
    "name": "recommend_across_lists"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
budgetNoOptional ceiling in USD/mo.
problemYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose real behavioral traits: the candidate pool is every published Top 11 list and results are ranked by relevance. However it says nothing about the response shape, whether results are cached/read-only, or how limit/budget interact with the ranking.

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

Conciseness5/5

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

Two sentences, zero filler, and the mechanism (what it pulls) is front-loaded before the usage condition. Every clause earns its place.

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 3-parameter read tool with a required 'problem' input, the description covers what it does and when to use it adequately. The one remaining gap is that, with no output schema present, it never sketches what a returned recommendation looks like.

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 only 33%: 'budget' is documented in-schema, while 'limit' and 'problem' have no descriptions. The description partially compensates by explaining that ranking is by relevance to the problem, and limit's bounds are already expressed structurally via min/max 1-11, but it never clarifies that limit caps the returned candidate count or how budget filters candidates.

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+resource ('Cross-list recommendation: pulls candidates from every published Top 11 list') and a ranking basis ('ranked by relevance to the problem'). It implicitly contrasts with the sibling 'recommend' by emphasizing the cross-list/every-published-list scope, though it never names that sibling explicitly, so the differentiation requires a small inference.

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?

'Use when the user's problem could span multiple categories' is a clear, actionable positive trigger. It stops short of stating when *not* to use it (e.g. a single-category problem, where the sibling 'recommend' or 'pick_one' would apply), so no explicit alternative is named.

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