Skip to main content
Glama
Sign In
Lagaam

Lagaam

Official
by lagaam-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List catalogs

list_catalogs
Read-only

Lists all catalogs, schemas, and tables you are allowed to query, so you can ground SQL and table descriptions in verified names instead of guessing.

Instructions

List every catalog, schema, and table you are allowed to query.

Call this first to ground yourself before describing tables or writing SQL — table names you have not seen here are guesses.

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_catalogs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
catalogsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.4

TDQS

A4.7/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 meaningful context beyond that: results are permission-scoped to what the caller may query, and the output is the authoritative source of valid table names. It does not discuss result size or pagination, which keeps it from 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?

Two short sentences, front-loaded with the scope statement and followed by the call-ordering instruction. Every clause carries actionable information with no filler.

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?

An output schema exists, so return values need not be described. For a zero-parameter, read-only discovery tool, the description covers purpose, ordering, and the risk of not calling it — nothing an agent needs is missing.

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 zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. No misleading parameter language is present.

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) and the exact resources returned (catalogs, schemas, tables), plus the scope qualifier 'you are allowed to query'. This also resolves the name/behavior mismatch implied by 'list_catalogs' by making clear it returns the full hierarchy.

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

Usage Guidelines5/5

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

Explicitly prescribes ordering ('Call this first') and the two downstream activities it precedes — describing tables and writing SQL — which map directly onto the siblings describe_table and query_data. It also states the consequence of skipping it: unseen table names are guesses.

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

Deploy Server

Other Tools