Wehome

Suggest Wehome searches

get_smart_suggestions

Read-onlyIdempotent

Use this when the user gives a partial or unclear place name and needs matching area or listing names on Wehome before searching. Returns text suggestions only.

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": {
      "q": "<q>"
    },
    "name": "get_smart_suggestions"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Partial keyword or query input (e.g., 'Hon')

Output Schema

Name	Required	Description	Default
`suggestions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior, so the description only needs to add context. 'Returns text suggestions only' usefully narrows expectations about output versus a real search. It doesn't discuss match semantics (prefix vs fuzzy) or suggestion count, which would be the remaining useful detail.

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 short sentences, zero waste, with the usage trigger front-loaded before the output caveat. Nothing 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 one-parameter, read-only suggestion tool with an output schema, the description plus annotations cover what an agent needs to decide and call it. The only gap is matching behavior (how partial the input can be, how many results come back), which is minor given the output schema.

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 single 'q' parameter is documented with an example ('Hon'), so the schema carries the load. The description adds only the notion that the input is a partial or unclear place name, which is a marginal restatement of the schema's own wording.

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?

States a specific verb and resource: it returns matching area or listing names for a partial place name on Wehome. The scope (names only, not full listings) is clear. It doesn't explicitly name the sibling search_accommodations, so differentiation is implied by 'before searching' rather than stated.

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?

'Use this when the user gives a partial or unclear place name' gives a concrete triggering condition, and 'before searching' establishes its position in the workflow ahead of the search tool. No explicit when-not or named alternative, so it falls short of a 5.

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

All Wehome 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?