Skip to main content
Glama
Sign In

Krusgraph

by com.krusgraph
OverviewDiscussions(1)Admin

List tables and columns

list_tables
Read-only

Lists the tables and their columns with types in one schema of a source. Requires workspace and source. Returns JSON with columns and types per table, or a column count per table when the answer is a summary. Read-only. Errors: {error, kind, hint}.

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": {
      "workspace": "<workspace>",
      "source": "<source>"
    },
    "name": "list_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNo"auto" (default: full up to 60 tables, else summary), "full" or "summary".auto
schemaNoSchema in the source. Default "dbo".dbo
sourceYesLakehouse, warehouse or SQL database, name or id.
tablesNoTable names or globs to show. Default all. Example: ["sales_*"].
workspaceYesFabric workspace, name or id.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / detail / description
      Added value: +"\"auto\" (default: full up to 60 tables, else summary), \"full\" or \"summary\"."
    • addedInput schema / properties / schema / description
      Added value: +"Schema in the source. Default \"dbo\"."
    • addedInput schema / properties / source / description
      Added value: +"Lakehouse, warehouse or SQL database, name or id."
    • addedInput schema / properties / tables / description
      Added value: +"Table names or globs to show. Default all. Example: [\"sales_*\"]."
    • addedInput schema / properties / workspace / description
      Added value: +"Fabric workspace, name or id."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly/openWorld/destructive, so the bar is low, yet the description adds real context: the two response shapes (columns+types vs. column count summary) and the error envelope shape {error, kind, hint}. It doesn't mention pagination or cost on large schemas, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the core action, then prerequisites, then return shape and errors. Minor redundancy: 'Read-only' repeats readOnlyHint=true, but nothing is padded.

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 read tool with full schema coverage, rich annotations and an output schema, this covers purpose, required inputs, return shape and error contract. The remaining gap is sibling disambiguation, which matters given the many schema-related tools in the list.

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?

Schema coverage is 100%, so the baseline is 3. The description only restates the required workspace/source and the full-vs-summary duality that the detail parameter already documents; it adds no new semantics such as glob behavior for tables or schema defaulting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: lists tables and their columns with types in one schema of a source. Clear scope (single schema, single source). It does not contrast itself with near-siblings like data_dictionary or analyze_schema, so an agent must infer the boundary.

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?

It states the prerequisites (requires workspace and source) which is genuinely useful context, but never says when to prefer this over data_dictionary or analyze_schema, nor when to use detail=summary vs full beyond the schema's own wording. Usage is implied as exploratory listing only.

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

All Krusgraph toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources