Skip to main content
Glama
Sign In
RushDB MCP Server

RushDB MCP Server

Official
by rush-db
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

resolveNames

Read-only

Finds the real label or property behind an uncertain name, ignoring case, separators, and plurals and ranking matches by spelling. Use it when a schema label or field is unknown instead of guessing.

Instructions

Find the real label or property behind a name you are unsure of (case, separators and plural endings ignored, then ranked by spelling): "patients" → Patient, "patients.birthdate" → Patient.Birthday. Call it instead of guessing when a label or field name is not in the schema. Returns [{ label, property?, score }].

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": {
      "text": "<text>"
    },
    "name": "resolveNames"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesA label, a property, or Label.property.
limitNoMost suggestions (default 5).

Output Schema

NameRequiredDescriptionDefault
namesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and closed-world, so safety is covered. The description adds genuinely new behavior: normalization rules (case, separators, plural endings ignored), spelling-based ranking, and the returned shape [{ label, property?, score }], which tells the agent to expect ranked candidates rather than a single answer.

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?

Front-loads the purpose, then examples, then the usage rule, then the return shape. Every clause carries information; nothing is redundant 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?

For a two-parameter lookup tool with an output schema and full annotation coverage, nothing an agent needs is missing: when to call it, what normalization it applies, and what the ranked result looks like are all stated.

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% and the schema already documents both text ("A label, a property, or Label.property") and limit (default 5). The description's examples reinforce the accepted text formats but add little beyond the schema, and it never mentions the limit parameter. Baseline 3 applies.

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: resolve an uncertain name to the real label or property, with concrete mapping examples ("patients" → Patient, "patients.birthdate" → Patient.Birthday). It clearly differs from schema-listing siblings such as findLabels, findProperties, and getSchema, which enumerate rather than resolve.

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 an explicit trigger condition: call it instead of guessing when a label or field name is not in the schema. It does not name findLabels/findProperties as the alternative for cases where the name IS known, but the usage context is unambiguous.

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