Skip to main content
Glama

Newest resident reviews

latest_reviews
Read-only

The newest reviews of residential buildings on AskResidents, optionally of one country.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "latest_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
countryNoTwo-letter country code, for example ES or RU

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered without the description. The description adds the source ('on AskResidents') and that results are 'newest' (recency-ordered), but omits whether a default limit applies or what fields a review contains. With annotations carrying the safety burden, this is adequate but thin.

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, front-loaded sentence with no filler. It is efficient, though its terseness is part of why other dimensions lose points.

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 no-required-parameter, read-only listing tool with no output schema, the definition covers the core purpose but leaves ordering guarantees, default result count, and the shape of returned reviews unstated. It is minimally sufficient rather than complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: country is documented in the schema itself with an example, but limit has no description at all. The description mentions the country dimension but adds no meaning beyond the schema, and says nothing about limit's range (1-20) or default behavior, so it fails to compensate for the coverage gap.

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 states a specific resource (newest reviews of residential buildings on AskResidents) and scope (optionally one country), so an agent knows exactly what it returns. It does not differentiate from the sibling search_address, but that tool targets a different resource type (addresses vs reviews), so the gap is minor.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'optionally of one country' hints at the country filter but gives no when-to-use guidance, no prerequisites, and no mention of when to prefer search_address or any other review source. An agent must infer the use case entirely from the noun phrase.

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