> ## Documentation Index
> Fetch the complete documentation index at: https://develop.cotality.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Prompts and resources

> Reusable prompt templates and reference resources for the market and trend analytics tools. Discover them with prompts/list and resources/list.

Beyond its tools, Cotality MCP exposes reusable prompt templates and reference resources for the market and trend analytics tools. They cost nothing extra to use and encode the calling patterns and domain conventions you would otherwise have to write yourself.

<Tip>
  Prompts are the fastest way to get good results from the analytics tools. They encode the
  correct geography type, time range shape, and metric selection for a given question, so your
  agent does not have to infer them.
</Tip>

## Discovering prompts and resources

Both follow the same request pattern as `tools/list`.

<CodeGroup>
  ```json List prompts theme={null}
  {
    "jsonrpc": "2.0",
    "id": 1,
    "method": "prompts/list"
  }
  ```

  ```json Get a prompt theme={null}
  {
    "jsonrpc": "2.0",
    "id": 2,
    "method": "prompts/get",
    "params": {
      "name": "analyze_market_trends_over_time",
      "arguments": {
        "geography_type": "county_fips_code",
        "geography_value": "06037",
        "start_year": 2024,
        "start_month": 1,
        "end_year": 2024,
        "end_month": 12
      }
    }
  }
  ```

  ```json List resources theme={null}
  {
    "jsonrpc": "2.0",
    "id": 3,
    "method": "resources/list"
  }
  ```

  ```json Read a resource theme={null}
  {
    "jsonrpc": "2.0",
    "id": 4,
    "method": "resources/read",
    "params": {
      "uri": "analytics://geography-reference"
    }
  }
  ```
</CodeGroup>

<Note>
  Like `tools/list`, these calls count against your [rate limit](/reference/rate-limits). Call
  them once when the session opens rather than before every tool call.
</Note>

## Prompts

Arguments shown with a default value are optional. All other arguments are required.

<Note>
  MCP prompt arguments are passed as strings. Where an argument is conceptually a number
  (`start_year`, `end_month`) or a list (`clips`), send it as a string or a JSON scalar — the
  server coerces it. This is different from tool arguments, which are validated against a strict
  JSON schema.
</Note>

### Market and trend analytics

| Prompt                            | Arguments                                                                                                                       | Purpose                                            |
| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------- |
| `analyze_market_trends_over_time` | `geography_type`, `geography_value`, `start_year`, `start_month`, `end_year`, `end_month`, `focus_area` (default `all metrics`) | Analyze how market metrics changed over a period   |
| `analyze_market_comparison`       | `geography_type`, `geography_values`, `metric_focus` (default `listing trends`)                                                 | Compare market metrics across multiple geographies |
| `evaluate_investment_opportunity` | `geography_type`, `geography_value`, `property_focus` (default `single-family`)                                                 | Evaluate a geography for investment potential      |
| `generate_market_report`          | `geography_type`, `geography_value`, `report_focus` (default `comprehensive`)                                                   | Produce a comprehensive market report              |
| `identify_market_anomalies`       | `geography_type`, `geography_value`, `comparison_geographies` (default empty)                                                   | Surface unusual patterns in market data            |
| `explain_geography_codes`         | none                                                                                                                            | Explain the geography types and code formats       |
| `format_time_range_query`         | `start_year`, `start_month`, `end_year`, `end_month`, `geography_type`, `geography_value`                                       | Build a correctly shaped time range query          |

## Resources

Address a resource by its **URI** — that is what `resources/read` takes. The **Name** column is
the display label the server registers; these resources register no explicit label, so they
surface under their function name.

| URI                                | Name                   | Format       | Contents                                             |
| ---------------------------------- | ---------------------- | ------------ | ---------------------------------------------------- |
| `analytics://geography-reference`  | `geography_reference`  | `text/plain` | Geography types and the code format each one expects |
| `analytics://query-examples`       | `query_examples`       | `text/plain` | Worked `analyticsFilter` examples                    |
| `analytics://tool-selection-guide` | `tool_selection_guide` | `text/plain` | Which analytics tool answers which question          |

<Tip>
  Load `analytics://geography-reference` and `analytics://tool-selection-guide` into your agent's
  context at session start. Together they prevent the two most common analytics mistakes —
  the wrong geography type and the wrong tool for the question.
</Tip>

## Scopes

Scope enforcement applies to **tools only**. Prompts and resources are not scope-filtered, so
`prompts/list` and `resources/list` can return entries for a server whose tools you cannot call.

<Warning>
  A prompt being listed does not mean you are entitled to the tools it tells the model to call.
  Confirm entitlement with `tools/list` before you build a
  flow around a prompt.
</Warning>

## Related

* [Market and trend analytics](/mcp/market-trend-analytics/tools/analytics) — the tools these prompts and resources support
* [Property data prompts and resources](/mcp/property-data/prompts-resources) — prompts and resources for the CLIP, property characteristics, and climate risk tools
* [Overview](/mcp/overview) — session lifecycle
* [Prompting patterns](/reference/prompting-patterns) — writing your own prompts