Skip to main content
Glama

GetRecord

Retrieve a specific record from the RushDB graph database by providing its unique ID, enabling quick access to stored data for AI agents and development teams.

Instructions

Get a specific record by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
recordIdYesID of the record to retrieve

Implementation Reference

  • The core handler function that executes the GetRecord tool logic: fetches a specific record by its ID from the database using db.records.findById and returns the data.
    export async function GetRecord(params: { recordId: string }) {
      const { recordId } = params
    
      const result = await db.records.findById(recordId)
    
      return result.data
    }
  • Input schema definition for the GetRecord tool, specifying that it requires a 'recordId' string parameter. This schema is used for tool listing and validation in the MCP server.
      name: 'GetRecord',
      description: 'Get a specific record by ID',
      inputSchema: {
        type: 'object',
        properties: { recordId: { type: 'string', description: 'ID of the record to retrieve' } },
        required: ['recordId']
      }
    },
  • index.ts:208-219 (registration)
    Registration and dispatch logic in the MCP server's CallToolRequestHandler: imports the GetRecord handler and invokes it in the switch statement when the tool is called, formatting the response as MCP content.
    case 'GetRecord':
      const record = await GetRecord({
        recordId: args.recordId as string
      })
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(record, null, 2)
          }
        ]
      }
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 states the tool retrieves a record but lacks behavioral details such as error handling (e.g., if ID is invalid), permissions required, or response format. This is a significant gap for a read operation with no annotation coverage.

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—'Get a specific record by ID'—front-loaded and appropriately sized for its purpose. Every word earns its place without redundancy.

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's simplicity (1 parameter, 100% schema coverage) but lack of annotations and output schema, the description is incomplete. It doesn't address behavioral aspects like what happens on failure or the return structure, which are crucial for agent invocation in a sibling-rich environment.

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%, with the parameter 'recordId' fully documented in the schema. The description adds no additional meaning beyond implying the ID is used for retrieval, matching the schema. Baseline 3 is appropriate as the schema does 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 clearly states the action ('Get') and resource ('a specific record'), specifying retrieval by ID. It distinguishes from siblings like FindRecords (general search) and GetRecordsByIds (bulk retrieval), though not explicitly named. However, it lacks full specificity about what 'record' entails in this context.

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

Usage Guidelines3/5

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

Usage is implied by the phrase 'by ID', suggesting this tool is for retrieving a single known record. No explicit guidance on when to use alternatives like FindOneRecord or GetRecordsByIds is provided, leaving some ambiguity for the agent in sibling-rich contexts.

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