Skip to main content
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.
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.

Discovering prompts and resources

Both follow the same request pattern as tools/list.
Like tools/list, these calls count against your rate limit. Call them once when the session opens rather than before every tool call.

Prompts

Arguments shown with a default value are optional. All other arguments are required.
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.

Market and trend analytics

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.
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.

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.
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.