Skip to main content
Glama

FindPropertyById

Retrieve property details using a unique ID from the RushDB graph database for efficient data access.

Instructions

Find a specific property by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
propertyIdYesID of the property to retrieve

Implementation Reference

  • The main handler function that implements the core logic of the FindPropertyById tool by querying the database for a property using its ID and returning the data.
    export async function FindPropertyById(params: { propertyId: string }) {
      const { propertyId } = params
    
      const result = await db.properties.findById(propertyId)
    
      return result.data
    }
  • Defines the tool's metadata including name, description, and input schema for validation and listing in MCP tool discovery.
    {
      name: 'FindPropertyById',
      description: 'Find a specific property by ID',
      inputSchema: {
        type: 'object',
        properties: { propertyId: { type: 'string', description: 'ID of the property to retrieve' } },
        required: ['propertyId']
      }
    },
  • index.ts:454-465 (registration)
    Registers the tool in the MCP server's CallToolRequest handler by dispatching calls to the FindPropertyById function and formatting the response.
    case 'FindPropertyById':
      const foundProperty = await FindPropertyById({
        propertyId: args.propertyId as string
      })
      return {
        content: [
          {
            type: 'text',
            text: foundProperty ? JSON.stringify(foundProperty, null, 2) : 'Property not found'
          }
        ]
      }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool finds a property but doesn't describe what happens if the ID is invalid (e.g., error handling), whether it's a read-only operation, or any performance considerations. This leaves significant gaps for a tool that likely queries data.

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, clear sentence with no wasted words. It's front-loaded with the core purpose, making it highly efficient and easy to parse.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., property details or null), error conditions, or how it differs from similar tools like 'FindProperties'. For a retrieval tool with no structured output documentation, this is inadequate.

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?

The input schema has 100% description coverage, with the parameter 'propertyId' documented as 'ID of the property to retrieve'. The description adds no additional semantic context beyond this, such as format examples or constraints, so it meets the baseline for high schema coverage.

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 tool's purpose as 'Find a specific property by ID', which includes both the verb ('Find') and resource ('property'). It distinguishes this from sibling tools like 'FindProperties' (plural retrieval) and 'GetRecord' (record-focused), though it doesn't explicitly mention these distinctions.

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. It doesn't mention prerequisites, such as needing a valid property ID, or compare it to siblings like 'FindProperties' (for multiple properties) or 'GetRecord' (for records).

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