ontario-data-mcp

Overview Schema Source Related Servers Discussions Admin

download_resource

Read-only

Download and cache a dataset resource locally in DuckDB for fast querying. Supports CSV, XLSX, JSON, and datastore-active resources.

Instructions

Download a dataset resource and cache it locally in DuckDB for fast querying.

Supports CSV, XLSX, JSON, and datastore-active resources. If already cached, returns staleness info so you can decide whether to refresh. Numeric columns stored as text are automatically cast to DOUBLE.

Workflow: search_datasets → get_dataset_info → download_resource → query_cached.

Args: resource_id: Prefixed resource ID (e.g. "toronto:abc123") or bare ID

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": {
      "resource_id": "<resource_id>"
    },
    "name": "download_resource"
  }
}

Input Schema

Name	Required	Description	Default
`resource_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2May 28, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds context about local caching, staleness info, supported formats, and automatic casting of numeric columns. No contradiction.

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?

The description is concise but includes essential info: purpose, supported formats, caching behavior, workflow, and parameter hint. It is front-loaded and avoids redundancy, though slightly dense.

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 low complexity (1 parameter, output schema exists, annotations present), the description covers all relevant aspects: formats, caching, casting, workflow, and parameter format. It is fully complete for its context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has one parameter with no description (0% coverage). The description adds format and examples (e.g., 'toronto:abc123' or bare ID), providing significant additional meaning beyond the schema.

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?

Description clearly states that the tool downloads and caches a dataset resource, supports specific formats, and places it in a workflow chain (search_datasets -> get_dataset_info -> download_resource -> query_cached). It distinguishes from sibling tools by specifying the caching and format handling.

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

Usage Guidelines4/5

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

The description provides a workflow and mentions caching behavior and auto-casting, implying when to use the tool. However, it does not explicitly state when not to use or provide alternatives, though the workflow guides usage well.

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