Skip to main content
Glama

El Trabajito directory

top_rated

Read-onlyIdempotent

The best-rated profiles in a category, optionally in one area, ranked by average rating and then by number of reviews: the answer to "who is a good X in Y". Unrated profiles come last and say so.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many profiles to return, up to 10 (default 5).
placeNoArea name; only areas with at least three profiles are listed separately, otherwise all of the category is returned.
categoryYesCategory slug from list_categories.
languageNoLanguage of the names and links in the answer (default es).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"How many profiles to return, up to 10 (default 5)."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent operation. The description adds useful behavioral detail beyond that: ranking is by average rating and then review count, and unrated profiles are placed last and identified as unrated.

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?

The description is a single tightly written sentence with the primary purpose and ranking behavior front-loaded. There is no redundant wording or repetition of schema details.

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?

The description covers the core return behavior, including ranking order and unrated handling, which is important because there is no output schema. It is nearly complete, though it does not describe the returned profile fields or the language effect on names and links.

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 explains all four parameters. The description only lightly reinforces the optional area filtering and does not add new parameter semantics beyond what the schema provides.

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 the resource and scope: best-rated profiles within a category, optionally filtered by area. It does not explicitly distinguish itself from siblings such as search_businesses, so it falls short of the top score.

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?

It gives a clear use case with the phrase 'the answer to "who is a good X in Y"', which tells the agent when this recommendation-style listing is appropriate. It does not mention exclusions or explicitly name alternative tools.

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