Skip to main content
Glama

GetSettings

Retrieve current database configuration and settings to verify setup and optimize performance in RushDB's graph database environment.

Instructions

Get the current database settings and configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the GetSettings tool. It retrieves the current database settings using the db.settings.get() method and returns the data.
    export async function GetSettings() {
      const result = await db.settings.get()
    
      return result.data
    }
  • The schema definition and metadata (name, description, inputSchema) for the GetSettings tool, used for tool listing and validation.
    {
      name: 'GetSettings',
      description: 'Get the current database settings and configuration',
      inputSchema: { type: 'object', properties: {}, required: [] }
    }
  • index.ts:532-541 (registration)
    The registration and dispatch logic in the MCP server's CallToolRequestSchema handler, which invokes the GetSettings function and formats the response.
    case 'GetSettings':
      const settings = await GetSettings()
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(settings, null, 2)
          }
        ]
      }
  • index.ts:72-76 (registration)
    The MCP server registration for listing tools, which includes GetSettings via the imported tools array.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools
      }
    })
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. While 'Get' implies a read operation, the description doesn't specify whether this requires special permissions, returns sensitive information, has rate limits, or provides a complete configuration snapshot. For a system settings tool with zero annotation coverage, this leaves significant behavioral gaps.

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 that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the essential information. Every word earns its place.

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

Completeness3/5

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

For a parameterless read operation with no output schema, the description is minimally adequate. It tells the agent what the tool does but lacks details about the return format, permission requirements, or system impact. Given the complexity is low (no parameters, simple retrieval), the description meets basic needs but could better prepare the agent for what to expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, and schema description coverage is 100% (though empty). The description appropriately doesn't discuss parameters since none exist. It correctly focuses on what the tool retrieves rather than how to parameterize it, meeting the baseline expectation for parameterless tools.

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 with a specific verb ('Get') and resource ('current database settings and configuration'). It distinguishes itself from siblings like GetRecord or GetRecordsByIds by focusing on system-level settings rather than data records. However, it doesn't explicitly differentiate from potential configuration-related siblings (none exist in the list).

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, appropriate contexts, or exclusions. Given the sibling tools include various data retrieval operations (GetRecord, FindRecords, etc.), the description should clarify this is for system configuration, not data retrieval.

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