Skip to main content
Glama

PropertyValues

Retrieve and filter property values from a graph database to support data-driven decisions and queries.

Instructions

Get values for a specific property

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
propertyIdYesID of the property to get values for
queryNoOptional search query for filtering values
orderByNoOrdering for value results
limitNoMax number of values to return
skipNoNumber of values to skip

Implementation Reference

  • The core handler function that executes the PropertyValues tool logic by querying the database for values associated with a specific property ID, supporting optional filters.
    export async function PropertyValues(params: {
      propertyId: string
      query?: string
      orderBy?: 'asc' | 'desc'
      limit?: number
      skip?: number
    }) {
      const { propertyId, query, orderBy, limit, skip } = params
    
      const searchQuery: Record<string, any> = {}
      if (query) searchQuery.query = query
      if (orderBy) searchQuery.orderBy = orderBy
      if (limit) searchQuery.limit = limit
      if (skip) searchQuery.skip = skip
    
      const result = await db.properties.values(propertyId, searchQuery)
    
      return result.data
    }
  • Input schema defining the parameters for the PropertyValues tool, including required propertyId and optional query, ordering, pagination.
    inputSchema: {
      type: 'object',
      properties: {
        propertyId: { type: 'string', description: 'ID of the property to get values for' },
        query: { type: 'string', description: 'Optional search query for filtering values' },
        orderBy: { type: 'string', enum: ['asc', 'desc'], description: 'Ordering for value results' },
        limit: { type: 'number', description: 'Max number of values to return' },
        skip: { type: 'number', description: 'Number of values to skip' }
      },
      required: ['propertyId']
    }
  • tools.ts:371-385 (registration)
    Registration of the PropertyValues tool in the tools array, including name, description, and schema; used by index.ts for MCP listTools.
    {
      name: 'PropertyValues',
      description: 'Get values for a specific property',
      inputSchema: {
        type: 'object',
        properties: {
          propertyId: { type: 'string', description: 'ID of the property to get values for' },
          query: { type: 'string', description: 'Optional search query for filtering values' },
          orderBy: { type: 'string', enum: ['asc', 'desc'], description: 'Ordering for value results' },
          limit: { type: 'number', description: 'Max number of values to return' },
          skip: { type: 'number', description: 'Number of values to skip' }
        },
        required: ['propertyId']
      }
    },
  • index.ts:44-44 (registration)
    Import of the PropertyValues handler function into the main index.ts for use in tool dispatching.
    import { PropertyValues } from './tools/PropertyValues.js'
  • index.ts:410-425 (registration)
    Dispatch case in the MCP CallToolRequest handler that invokes the PropertyValues function and formats the response.
    case 'PropertyValues':
      const propertyValues = await PropertyValues({
        propertyId: args.propertyId as string,
        query: args.query as string | undefined,
        orderBy: args.orderBy as 'asc' | 'desc' | undefined,
        limit: args.limit as number | undefined,
        skip: args.skip as number | undefined
      })
      return {
        content: [
          {
            type: 'text',
            text: propertyValues ? JSON.stringify(propertyValues, null, 2) : 'No property values found'
          }
        ]
      }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It implies a read operation ('Get'), but doesn't disclose behavioral traits like whether it's safe, if it requires authentication, rate limits, pagination behavior (beyond schema parameters), or what the output looks like. For a tool with 5 parameters and no output schema, this is a significant gap in transparency.

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 waste. It's front-loaded and appropriately sized for the tool's purpose, making it easy to parse quickly.

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?

Given the tool has 5 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain the return values, error conditions, or behavioral context needed for effective use. For a data retrieval tool with filtering and ordering, more context is warranted to compensate for the lack of structured metadata.

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 already documents all parameters (propertyId, query, orderBy, limit, skip) with descriptions. The description adds no additional meaning beyond the schema, such as examples or context for parameter use. Baseline 3 is appropriate as the schema handles the heavy lifting.

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 'Get values for a specific property' clearly states the action (Get) and resource (values for a property). It distinguishes from siblings like FindProperties (which likely lists properties) or GetRecord (which retrieves records), but doesn't explicitly differentiate them. The purpose is specific but lacks sibling comparison details.

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?

No guidance on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites, context, or exclusions. For example, it doesn't clarify if this is for retrieving metadata values versus data values, or when to use FindRecords instead. This leaves usage ambiguous.

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