Skip to main content
Glama

NYSgpt Data Library

List databases

list_databases
Read-only

List the databases in the NYSgpt Data Library. Each database is one subject of public records (for example govblock_awards = federal spending, govblock_patents, govblock_sec = company filings, govblock_scholarly = OpenAlex, govblock_labor, govblock_census, govblock_energy, govblock_health, govblock_courts). Call this first, then list_tables.

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": "list_databases"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds behavior beyond that: it is a non-parameterized enumeration whose items are subject domains, and it establishes the workflow position ('call this first'), which annotations cannot convey. It does not describe result size or ordering, a minor omission for a static catalog.

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 core purpose and the 'call this first' instruction are front-loaded in the first and last clauses. The parenthetical list of eight example databases is longer than strictly necessary but does real work by teaching the agent what a subject-level database looks like, so it mostly earns its space.

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?

For a simple zero-argument discovery tool with no output schema, the description covers purpose, granularity, examples, and sequencing. The one gap is the shape of the return value — whether entries are bare names, ids, or name-plus-description objects — which the agent must discover at call time.

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 tool takes no parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The schema's empty object with additionalProperties=false is fully consistent with the described behavior.

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 and resource ('List the databases in the NYSgpt Data Library') and immediately clarifies the unit of granularity ('Each database is one subject of public records'), so an agent knows this returns subject-level containers rather than tables. The closing 'Call this first, then list_tables' distinguishes it from the sibling that operates one level down.

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?

Gives explicit sequencing guidance — this is the entry point, followed by list_tables — which is the key routing decision for a discovery tool. It does not name when NOT to use it (e.g., if the database name is already known, skip to list_tables or query), but for a zero-parameter root tool the guidance is clear and actionable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.