How Socials Homes works: pricing, FAQ, a terms summary and housing guides for people moving abroad.
Scored across 1 tool
There is only one tool, so there is no possibility of confusing it with another. Its purpose (keyword search across the docs) is stated plainly and unambiguously.
The single tool uses a clear snake_case verb_noun pattern (search_docs) that matches its action. With no other tools to contradict it, naming is fully consistent.
A single search tool is defensible for a documentation Q&A server, but 1 tool is thin for the stated scope covering pricing, FAQ, terms, and multiple housing guides. It borders on under-scoped.
Search covers discovery, but there is no tool to list available docs or fetch/read a full document — the tool returns a resource URI, which is a dead end unless resources are separately exposed to the agent. Notable gaps exist beyond search.
Keyword search across the Socials Homes documentation: how it works, pricing, FAQ, terms summary and the housing guides for moving abroad. Returns the best-matching sections with a snippet, the resource URI to read in full, and the web page to cite.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many results to return, 1 to 10. Defaults to 5. | |
| query | Yes | Keywords or a question, for example "cancel subscription" or "documents to rent in Germany". |
| Name | Required | Description |
|---|---|---|
| query | Yes | |
| results | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds genuine behavioral value by stating this is *keyword* search and describing what a result contains (snippet, resource URI, web page to cite), which tells the agent how to act on output even though an output schema exists.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single tight sentence front-loads the core action and scope, then closes with the return shape. No filler, appropriately sized.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With rich annotations, a full output schema, and 100% parameter documentation, the description only needs to establish corpus scope and search mode, which it does. Nothing an agent requires to call it correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and both parameters (query, limit) are fully documented in the schema with examples and bounds. The description adds nothing about parameter usage, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (keyword search) and resource (Socials Homes documentation), then enumerates the covered content areas (how it works, pricing, FAQ, terms, housing guides). An agent immediately knows what corpus is searched and that matching is lexical, not semantic.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There are no sibling tools to differentiate from, and the description implies its purpose without stating when to reach for it versus answering directly. Adequate but no explicit when-to-use guidance or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
search_docsSearch and read city guides, student blog guides, the FAQ, pricing and policies.
Guides, housing, jobs, events and communities for foreigners living in France, in 6 languages.
Country guides, customs rules, mover directory and quote requests for 155+ countries
City guides, local business listings and Q&A for expats and newcomers in cities worldwide.
Add one secure layer between your agents and this server.