@marocain/mcp-server

get_market

Retrieve macro market facts for a Moroccan city or nationwide—median prices, supply, momentum, and catalysts like WC2030 or TGV—to benchmark investment decisions.

Instructions

Macro market facts for a city or national scope — median price, supply, momentum and the catalysts (WC2030, TGV) the {GIN} Deal pillar is benchmarked against.

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": {
      "scope": "<scope>"
    },
    "name": "get_market"
  }
}

Input Schema

Name	Required	Description	Default
`scope`	Yes	City slug (e.g. marrakech) or 'morocco' for national.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.9Aug 14, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the type of data returned and the geographic scope, but does not mention data freshness, error cases, or read-only semantics. It adds useful context but lacks full behavioral transparency.

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 a single, information-dense phrase that front-loads the tool's purpose and key data points. Every word contributes value, with no filler or redundant information.

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?

Given the tool's simplicity (one parameter, no annotations, no output schema), the description provides sufficient context by listing the data content and the benchmarking context. It does not include return format or error handling, but for a straightforward market-facts tool, this is adequately 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?

The input schema has 100% coverage of the single parameter 'scope', including an example. The description adds the 'macro' context but does not provide additional parameter-level syntax or format details. Baseline 3 is appropriate given the high schema coverage.

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 specifies the tool's function: providing macro market facts for a city or national scope. It lists concrete data points (median price, supply, momentum, catalysts) and mentions the GIN Deal pillar, distinguishing it from sibling tools like search_listings or get_gin_score.

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?

The description implies usage when macro market data is needed and mentions benchmarking for the GIN Deal pillar, but it does not explicitly state when to use this tool versus alternatives or provide any exclusions. No alternative tools are referenced.

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

Deploy Server