Skip to main content
Glama

El Trabajito directory

get_business_reviews

Read-onlyIdempotent

Customer reviews of one profile, newest first (rating, text, date, first name and initial). Reviews are written by signed-in users; the directory does not verify that the reviewer hired the person.

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": {
      "slug": "<slug>"
    },
    "name": "get_business_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage of reviews, newest first, starting at 1 (default 1).
slugYesThe profile slug, exactly as returned by search_businesses or top_rated (for example "carlos-jimenez").
limitNoReviews per page, up to 10 (default 5).
languageNoLanguage of the names and links in the answer (default es).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Reviews per page, up to 10 (default 5)."
    • addedInput schema / properties / page / description
      Added value: +"Page of reviews, newest first, starting at 1 (default 1)."
    • addedInput schema / properties / page / maximum
      Added value: +50
    • addedInput schema / properties / slug / description
      Added value: +"The profile slug, exactly as returned by search_businesses or top_rated (for example \"carlos-jimenez\")."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuinely extra behavioral context: reviews are authored by signed-in users and the directory does not verify that a reviewer hired the person — an important trust caveat an agent would otherwise not know. Ordering ('newest first') and result fields are also disclosed.

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 tight sentences: the first front-loads what is returned and in what order, the second delivers the trust caveat. Nothing is redundant or padded.

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 read-only, single-resource listing with no output schema, the description supplies the return shape, ordering, and a data-quality caveat, while paging and language are fully specified in the schema. An agent has enough to call it correctly; only explicit sibling routing is missing.

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 page, limit, slug and language are all documented in the schema; the baseline of 3 applies. The description only reinforces ordering and the slug's origin, adding little beyond what the structured fields already say.

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 specific verb+resource ('customer reviews of one profile') and enumerates what a review contains (rating, text, date, first name and initial), so it is instantly distinguishable from get_business or search_businesses. It stops short of explicitly stating how it differs from those siblings, keeping it at 4 rather than 5.

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?

Usage is only implied: 'of one profile' plus the schema note that slug comes from search_businesses or top_rated tells an agent it operates on a single already-identified business. There is no explicit when-to-use/when-not statement or named alternative, so guidance is adequate but inferential.

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