Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

notion-mcp__notion_get_database

Read-only

Reads one Notion database and the schema of each of its data sources. In Notion's current API a database is a container of one or more data sources, and rows and properties live on the data source; most databases have one. Returns the database's id, title, url, parent and in_trash, and data_sources: for each, its id, name and properties as a list of {name, type}, with options (the option names) for select, multi_select and status properties. The data source id is the one notion_query_data_source takes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "database_id": "<database_id>"
    },
    "name": "notion-mcp__notion_get_database"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
database_idYesThe database's Notion id, with or without dashes, or a Notion URL that contains it (the id is read from the URL).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description goes further and enumerates the returned fields (id, title, url, parent, in_trash, data_sources with properties and select/multi_select/status options). It does not mention permission or sharing requirements, which is the one gap beyond the supplied annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the data-model disambiguation are front-loaded, and the return-value enumeration is dense but earns its place because there is no output schema. A few clauses, such as the parenthetical '(the option names),' could be trimmed slightly, but nothing is redundant.

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?

With no output schema, the description must describe the response shape, and it does so thoroughly, including nested data_sources and property {name, type} entries. It is only incomplete in omitting error/permission behavior and whether the call is paginated.

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 database_id documented as accepting a dashed/undashed id or a Notion URL and account documented as an optional email selector. The description adds no further semantics about either parameter, so the schema carries the full load and baseline 3 applies.

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 opens with a specific verb and resource ('Reads one Notion database') and immediately disambiguates it from notion_query_data_source by explaining that rows and properties live on the data source, not the database. An agent can tell exactly which of the two read tools it needs without opening either schema.

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

Usage Guidelines4/5

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

It gives clear context for use — fetch the container and its schema before querying — and explicitly states 'The data source id is the one notion_query_data_source takes,' which encodes the sequencing between the two tools. It stops short of an explicit when-not or a statement about chained prerequisites for create/update, so it is strong but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All DataToRAG toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources