Skip to main content
Glama

relentless_list_databases

Discover available Notion databases connected to your Relentless account to identify data sources for reading and writing operations.

Instructions

List all Notion databases connected to your Relentless account. Use this first to discover available databases, then use other tools to read/write data. Returns database names that can be used with other tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'relentless_list_databases' tool. It calls the listDatabases helper, formats the result into MCP text content, and returns it.
    case 'relentless_list_databases': {
      console.error(`[${new Date().toISOString()}] Listing databases`)
    
      const databases = await listDatabases()
    
      return {
        content: [
          {
            type: 'text',
            text: `Found ${databases.count} database(s):\n\n${JSON.stringify(
              databases.databases,
              null,
              2
            )}`,
          },
        ],
      }
    }
  • src/index.ts:206-215 (registration)
    Tool registration in the ListToolsRequestSchema handler, defining the tool name, description, and input schema (empty object, no parameters required).
    {
      name: 'relentless_list_databases',
      description:
        'List all Notion databases connected to your Relentless account. Use this first to discover available databases, then use other tools to read/write data. Returns database names that can be used with other tools.',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • Helper function that performs the API request to list all available databases from the Relentless API.
    async function listDatabases(): Promise<any> {
      try {
        const endpoint = `${RELENTLESS_API_BASE}/api/v1/public/databases`
        return await relentlessRequest(endpoint, undefined, 1)
      } catch (error) {
        console.error(`⚠️  Could not fetch databases: ${error}`)
        throw error
      }
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the return value ('Returns database names that can be used with other tools') which is helpful, but doesn't mention potential limitations like rate limits, authentication requirements, or error conditions. The description adds some behavioral context but leaves gaps in operational 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 perfectly concise with three focused sentences that each serve a distinct purpose: stating the action, providing usage guidance, and describing the return value. There's zero wasted language, and the information is front-loaded with the core purpose stated first.

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

Completeness4/5

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

For a zero-parameter discovery tool with no output schema, the description provides excellent context about what the tool does, when to use it, and what it returns. It could be slightly more complete by mentioning any limitations or prerequisites, but given the tool's simplicity and the absence of annotations, it covers the essential information well.

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 with 100% schema description coverage, so the schema already fully documents the input requirements. The description appropriately doesn't waste space discussing non-existent parameters, maintaining focus on the tool's purpose and usage. This earns a baseline 4 for parameter handling in a zero-parameter tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('List all Notion databases'), identifies the resource ('connected to your Relentless account'), and distinguishes it from siblings by explaining its role in discovery before using other tools. It provides a complete purpose statement that goes beyond a simple tautology.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool ('Use this first to discover available databases') and provides clear alternatives ('then use other tools to read/write data'). It gives specific guidance on the workflow sequence and distinguishes it from sibling tools like relentless_read or relentless_insert.

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/PranaytheSingh/relentless-mcp'

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