Skip to main content
Glama

Best of a category

get_best_of
Read-onlyIdempotent

The Published providers in one category, in the order its category page prints (ranked by what we can confirm: a public price, an API and docs, independent sources, stated limits), as a markdown answer sheet. Payment never moves a row.

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": {
      "category": "<category>"
    },
    "name": "get_best_of"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYesThe category slug (from list_categories).

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 already cover read-only, non-destructive, idempotent behavior, but the description adds useful behavioral context: the ranking criteria and the guarantee that payment never affects row order. It also discloses the markdown answer-sheet output format.

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 description is compact and front-loads the resource and scope. The ranking details are useful, though the long parenthetical makes it slightly dense rather than maximally clean.

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 one-parameter read-only tool with rich annotations and no output schema, the description covers purpose, ranking behavior, output format, and integrity constraints. It is complete enough to invoke correctly, with only minor room to clarify sibling routing.

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 coverage is 100%, and the schema already explains that category is a slug from list_categories. The description adds only that the tool operates on 'one category,' so the baseline score of 3 is appropriate.

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 clearly states that it returns Published providers in a single category, ranked in the category page order, as a markdown answer sheet. It is more specific than the title alone, but it does not explicitly contrast itself with siblings such as search_listings or compare_listings.

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 intended use is implied by 'Best of a category' and the category-scoped output, but the description gives no explicit when-to-use guidance, prerequisites, or named alternatives for choosing between this and search_listings/compare_listings.

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