Skip to main content
Glama
Waterboards MCP Server

Waterboards MCP Server

List waterboard datasets

waterboards_list_datasets
Read-onlyIdempotent

List available California water datasets (Gold views) exposed by this server, including table names and comments, with pagination, to discover which drinking water data you can query.

Instructions

List the water datasets (Gold views) available through this server.

Source: Unity Catalog information_schema for the configured Gold schema. Refresh cadence: reflects the current catalog; underlying data refresh varies by dataset (see each view's comment).

Returns a pagination envelope; each result has table_name and table_comment.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "waterboards_list_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
paginationNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely useful context beyond them: the data source (Unity Catalog information_schema for the configured Gold schema), a refresh-cadence caveat that underlying data varies per view, and the shape of the return. It does not state auth/permission requirements, which keeps it short of a 5.

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?

Four short, labelled sentences, each earning its place: what it lists, where the data comes from, a freshness caveat, and the return shape. Front-loaded with the core action.

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 an output schema present and rich read-only annotations, the description does not need to explain return values, yet it helpfully summarises them. What remains unaddressed is whether the listing is scoped/filtered by catalog permissions or returns everything in the Gold schema.

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?

Reported schema description coverage is 0%, so the description nominally carries the burden, and it only mentions the pagination envelope on the output side, not the limit/offset inputs. The nested schema does in fact document limit (1-100) and offset, so the agent is not fully in the dark, but the description adds no input-level semantics of its own.

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?

States a specific verb (List) plus a specific resource (water datasets / Gold views) and scopes it to this server. It reads as a metadata-discovery tool, which cleanly separates it from siblings like waterboards_get_water_system or waterboards_get_source_chemistry_near_zip that return actual data.

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 phrase 'available through this server' implies this is a discovery/first-step tool, but there is no explicit 'use this before calling X' or 'do not use this to retrieve measurements' guidance. The when-to-use is inferable rather than stated, so a 3 is warranted.

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