EPK Properties Public Knowledge MCP

Search EPK public knowledge

search

Read-onlyIdempotent

Use this for EPK public knowledge searches and always when one request combines property listings with guides, regulations, taxes, residency, relocation, or due diligence. It returns both result types in one response and remains compatible with company knowledge and deep research.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	Natural-language search query.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	Yes

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds behavioral context about the combined response type and compatibility with company knowledge/deep research, which goes beyond annotations without contradicting them.

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?

The description is two sentences, front-loaded with the primary purpose, and every sentence serves a distinct function: usage guidance and behavior/benefit. No redundancy or unnecessary detail.

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 the output schema exists and annotations are rich, the description adequately covers usage, combined result behavior, and compatibility. For a simple one-parameter search tool, it is complete.

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% with the query parameter described as 'Natural-language search query'. The description does not add parameter-specific details, so the baseline 3 applies.

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 clearly states the tool's purpose: 'Use this for EPK public knowledge searches' and specifies it returns 'both result types in one response', distinguishing it from siblings like search_guides and search_properties.

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

Usage Guidelines5/5

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

It provides explicit usage guidance: 'always when one request combines property listings with guides, regulations, taxes, residency, relocation, or due diligence' and implies alternatives for non-combined queries via the sibling tools.

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

All EPK Properties Public Knowledge MCP tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation4/5

The search tools are clearly separated by scope (combined vs guides-only vs properties-only), and the getters are typed by resource. However, `fetch` overlaps conceptually with `get_property` and `get_guide_section` because it also retrieves full property or guide documents, relying on a different ID type to distinguish itself.

Naming Consistency4/5

Most tools follow a clear verb_noun pattern: search/search_guides/search_properties and get_guide_section/get_property. The single bare `fetch` breaks the pattern and uses a synonym for `get`, creating a minor but noticeable inconsistency.

Tool Count5/5

Six tools is a tight, well-scoped set for a public knowledge server covering properties and guides. Each tool serves a distinct query or retrieval need, and none feel redundant or out of place.

Completeness5/5

The set covers combined and filtered searching plus retrieval for property details, guide sections, and full public documents. For a read-only public knowledge domain, this is a complete lifecycle with no obvious dead ends.

Resources

Need Help?