Muscat Properties catalogue

One project in full

get_project

Read-onlyIdempotent

Every published fact of one project: developer, area, status, handover, starting price and price per square metre in OMR, sizes, bedrooms, units, ownership, residency, payment plans, amenities, key distances, the opening answer and the FAQ.

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": {
      "slug": "<slug>"
    },
    "name": "get_project"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No	Language of the answer. Default en.
`slug`	Yes	The project slug, the last part of its URL, e.g. as in https://muscat.properties/projects/<slug>

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered. The description still adds real value by disclosing the breadth of the payload — including narrative fields like the opening answer and FAQ — which tells the agent to expect a large, complete record rather than a summary. It does not say what happens for an unknown or unpublished slug.

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 starting with the scope ('Every published fact of one project'), followed by an enumeration that earns its length by previewing the return payload. The list is dense but not padded with filler or restated title text.

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?

With no output schema, the description carries the burden of describing return values and does so thoroughly, covering pricing, units, amenities and FAQ content. The remaining gap is operational: no mention of error behavior for missing slugs or how the slug is discovered via search_projects.

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 both slug and the lang enum documented in the schema (including a URL example for slug), so the description need not repeat them. It adds nothing about parameter semantics beyond what structured fields already provide, so the baseline 3 applies.

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 clear resource and scope: 'every published fact of one project', and enumerates the returned fields (developer, area, price in OMR, payment plans, FAQ), which makes the retrieval footprint unmistakable. It does not explicitly contrast itself with search_projects, so sibling differentiation comes from the title ('One project in full') rather than the description itself.

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

Usage Guidelines3/5

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

Usage is only implied: the phrasing 'one project' plus the title's 'in full' suggests this is the detail lookup after a search, but no alternative is named and no prerequisite (e.g. get the slug from search_projects) is stated. An agent can infer the role but must guess the workflow.

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

All Muscat Properties catalogue 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?