Skip to main content
Glama
Sign In
RushDB MCP Server

RushDB MCP Server

Official
by rush-db
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

getSchemaSummary

Read-only

Retrieve a live schema summary of labels, property types, value counts, ranges, distinct values, and relationships in one read to understand how data is coded without field-by-field calls.

Instructions

Every label with its properties in one live read (never cached): per property its type, record count, exact distinct count, min/max for numbers and dates, and the full value list when it holds few (fewValues, default 10); per label its relationships. Use it to learn how values are coded (e.g. KCT holds "-" and "+") without one call per field.

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

Input Schema

NameRequiredDescriptionDefault
labelsNoLabels to summarize (all when omitted).
fewValuesNoList values of properties with at most this many (default 10, max 100).

Output Schema

NameRequiredDescriptionDefault
labelsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.1.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered; the description adds the notable behavioral trait that the read is live and never cached. It also discloses the fewValues truncation default (10), which tells the agent when the full value list will not appear.

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 output contents are front-loaded in a single colon-delimited sentence, followed by a short usage sentence; nearly every clause carries information. It is dense with parentheticals and semicolon sub-clauses, which slightly impedes scanning but does not waste words.

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, the description need not restate return fields, yet it still conveys freshness and truncation behavior plus a motivating use case. For a two-parameter read tool that is sufficient; only explicit sibling differentiation is missing.

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 description coverage is 100%, so both parameters (labels, fewValues) are already documented, and the description merely repeats the fewValues default of 10. The implied "every label when labels omitted" behavior is a small addition beyond the schema, matching the baseline 3 for fully documented params.

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?

The description states precisely what is returned: per-label properties with type, record count, exact distinct count, min/max, and value lists, plus per-label relationships. That is a specific verb+resource picture, but it never names or contrasts the close siblings getSchema, getSchemaMarkdown, or propertyValues, leaving the agent to infer the difference.

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?

"Use it to learn how values are coded (e.g. KCT holds \"-\" and \"+\") without one call per field" gives a concrete when-to-use and the efficiency rationale versus per-field calls. It stops short of explicit exclusions or naming the alternative tools (getSchema, propertyValues), so it is clear context rather than full routing guidance.

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