Skip to main content
Glama

FindProperties

Search and retrieve property data from RushDB's graph database using customizable filters, sorting, and pagination for efficient data access.

Instructions

Find properties in the database using a search query

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
whereNoSearch conditions for finding properties
limitNoMaximum number of properties to return
skipNoNumber of properties to skip
orderByNoSorting configuration: key = field, value = asc|desc

Implementation Reference

  • The core handler function that executes the tool logic: queries the database for properties using where, limit, skip, and orderBy parameters.
    export async function FindProperties(params: {
      where?: Record<string, any>
      limit?: number
      skip?: number
      orderBy?: Record<string, 'asc' | 'desc'>
    }) {
      const { where, limit, skip, orderBy } = params
    
      const searchQuery: Record<string, any> = {}
      if (where) searchQuery.where = where
      if (limit) searchQuery.limit = limit
      if (skip) searchQuery.skip = skip
      if (orderBy && Object.keys(orderBy).length > 0) searchQuery.orderBy = orderBy
    
      const result = await db.properties.find(searchQuery)
      return result.data
    }
  • Input schema and metadata for the FindProperties tool, defining parameters where, limit, skip, orderBy.
    {
      name: 'FindProperties',
      description: 'Find properties in the database using a search query',
      inputSchema: {
        type: 'object',
        properties: {
          where: { type: 'object', description: 'Search conditions for finding properties' },
          limit: { type: 'number', description: 'Maximum number of properties to return', default: 10 },
          skip: { type: 'number', description: 'Number of properties to skip', default: 0 },
          orderBy: {
            type: 'object',
            description: 'Sorting configuration: key = field, value = asc|desc',
            additionalProperties: { type: 'string', enum: ['asc', 'desc'] }
          }
        },
        required: []
      }
  • index.ts:427-442 (registration)
    Tool registration in the main MCP server request handler: switch case that invokes FindProperties and formats the response.
    case 'FindProperties':
      const foundProperties = await FindProperties({
        where: args.where as Record<string, any> | undefined,
        limit: args.limit as number | undefined,
        skip: args.skip as number | undefined,
        orderBy: args.orderBy as Record<string, 'asc' | 'desc'> | undefined
      })
      return {
        content: [
          {
            type: 'text',
            text:
              foundProperties.length > 0 ? JSON.stringify(foundProperties, null, 2) : 'No properties found'
          }
        ]
      }
  • index.ts:72-75 (registration)
    Registers the list of all tools (including FindProperties schema) for MCP ListTools requests.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools
      }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it's a search operation. It doesn't disclose whether this is read-only (implied but not explicit), potential performance impacts, pagination behavior beyond the limit/skip parameters, or what happens with empty results. For a search tool with 4 parameters, this is insufficient behavioral context.

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?

The description is a single, efficient sentence with zero wasted words. It's appropriately sized for a search tool and front-loads the core purpose without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a search tool with 4 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'properties' refer to in this database context, what fields are searchable, the return format, or error conditions. The agent lacks sufficient context to use this tool effectively compared to siblings.

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 the schema fully documents all 4 parameters. The description adds no additional parameter semantics beyond implying a 'search query' maps to the 'where' parameter. This meets the baseline for high schema coverage but doesn't enhance understanding.

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 clearly states the verb ('Find') and resource ('properties in the database'), specifying it's a search operation. However, it doesn't distinguish this tool from sibling tools like FindRecords, FindOneRecord, or FindPropertyById, which also retrieve data from the database.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like FindRecords or FindPropertyById. It mentions 'using a search query' but doesn't clarify if this is for general property searches versus more specific sibling tools, leaving the agent without context for selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rush-db/RushDB'

If you have feedback or need assistance with the MCP directory API, please join our Discord server