Skip to main content
Glama
RushDB MCP Server

RushDB MCP Server

Official
by rush-db

propertyValues

Read-only

Retrieves min/max statistics for numeric or datetime properties and distinct values for string/boolean fields, enabling range queries and filter value canonicalization.

Instructions

Get statistics or distinct values for a specific property, identified by the id field returned from findProperties. What this tool returns depends on the property type: • number / datetime → returns { min, max } — use this to answer range, min/max, or spread questions for numeric or date fields. No findRecords aggregation needed. • string / boolean → returns a list of all distinct values — use this to canonicalize filter values before querying. Workflow for range/min/max questions: (1) findLabels, (2) findProperties to find the field and get its id and type, (3) call this tool with that id if type is number or datetime.

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": {
      "propertyId": "<propertyId>"
    },
    "name": "propertyValues"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNoNumber of string values to skip.
limitNoMax number of string values to return.
matchNoHow `query` matches (default contains). `similar` finds near spellings (spiderman → Spider-Man).
queryNoOptional text filter: keep the values whose text matches (strings as stored; numbers and dates as shown; a date such as 1993/11/12 or 2013-06 also matches that date in another layout). Matching values come ranked by record count, with counts.
orderByNoSort order for string value lists.
propertyIdYesThe `id` field from the property object returned by findProperties.
domainOnMissNoWhen nothing matches and the property holds at most this many distinct values, return all of them instead (searchMissed: true): the data may store the idea as a code ("positive" → "+").

Output Schema

NameRequiredDescriptionDefault
propertyValuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.1.1
    • addedInput schema / properties / domainOnMiss
      Added value: +{
      +  "description": "When nothing matches and the property holds at most this many distinct values, return all of them instead (searchMissed: true): the data may store the idea as a code (\"positive\" → \"+\").",
      +  "type": "number"
      +}
    • addedInput schema / properties / match
      Added value: +{
      +  "description": "How `query` matches (default contains). `similar` finds near spellings (spiderman → Spider-Man).",
      +  "enum": [
      +    "contains",
      +    "prefix",
      +    "exact",
      +    "similar"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"Optional text filter — only applies to string properties."New value: +"Optional text filter: keep the values whose text matches (strings as stored; numbers and dates as shown; a date such as 1993/11/12 or 2013-06 also matches that date in another layout). Matching values come ranked by record count, with counts."
  2. First observedv3.0.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real behavioral detail: the return shape varies by property type, query matches come 'ranked by record count, with counts', and domainOnMiss triggers a searchMissed fallback. It stops short of describing pagination behavior, error cases for a bad propertyId, or behavior when the property type is unsupported.

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?

Front-loaded with the tool's purpose, then type-driven outcomes as bullets, then a compact numbered workflow — easy to scan. The closing workflow sentence partially restates the earlier bullets (type must be number or datetime), costing some redundancy.

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 7-parameter read-only query tool with a full schema and an output schema, the description covers the essential unknowns: what varies in the response by property type, how to obtain the required id, and the intended multi-step workflow. Nothing an agent needs in order to invoke it correctly 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 every parameter (including match enum, query cross-format matching, and domainOnMiss) is already documented in the schema. The description's only parameter-level contribution is restating that the id comes from findProperties and that type governs the result, which largely duplicates the schema's own propertyId description. 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 (get statistics / distinct values) and resource (a property identified by id), and explicitly branches the outcome by property type (number/datetime → {min,max}; string/boolean → distinct list). It also contrasts itself with the aggregation alternative ('No findRecords aggregation needed'), so an agent can distinguish it from siblings like findRecords or searchValues.

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?

Gives explicit when-to-use conditions ('use this to answer range, min/max, or spread questions', 'canonicalize filter values before querying') and a numbered workflow (findLabels → findProperties → propertyValues) that names the prerequisites. It also implicitly excludes cases by stating the type condition (only if type is number or datetime).

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