Avecindar rental search

Read a rental home

get_home

Read-onlyIdempotent

Read one publicly displayed rental home by its id: costs, conditions, areas, photos and provenance. Availability is not confirmed unless availability.confirmed is true (confirmed within the last seven days). Imported listings link to their original source; their text and photos are third-party content, not verified facts. Unknown costs are null, never zero.

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": {
      "id": "<id>"
    },
    "name": "get_home"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 19, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it reveals availability.confirmed semantics ('confirmed within the last seven days'), states that imported listings are unverified third-party content, and clarifies that unknown costs are null rather than zero. These caveats materially change how an agent should interpret results.

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?

Three sentences with no filler; the primary action is in the first sentence, followed by high-value caveats about availability, provenance, and null semantics. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description still tells the agent what data categories to expect and how to interpret ambiguous values. Availability freshness, source provenance, and null cost semantics are the likely failure points and are all addressed. No critical behavioral information appears missing.

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

Parameters4/5

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

The schema only defines id as a string with maxLength 100, and the description reinforces that the id must identify a publicly displayed rental home. Since it is a single self-explanatory parameter, the lack of additional parameter prose does not hurt usability.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Read one publicly displayed rental home by its id' – a specific verb, a clear resource, and a unique retrieval mode. It also enumerates the returned content (costs, conditions, areas, photos, provenance), which distinguishes it from sibling list/search tools.

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 clearly communicates that the tool is for fetching a single known rental home by id, implying it is not for discovery or browsing. It does not explicitly name search_homes or exclude alternatives, but the by-id target is unambiguous context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Avecindar rental search tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?