Skip to main content
Glama

Notion_connect

by io.github.pipeworx-io

Notion Get Database

notion_get_database
Read-onlyIdempotent

Get a Notion database schema by ID. Returns all properties, field types, and configuration to understand structure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
database_idYesNotion database ID (UUID format, with or without dashes)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoDatabase ID
urlNoNotion web URL for the database
titleNoDatabase title content blocks
objectNoObject type ('database')
parentNoParent object reference
archivedNoWhether database is archived
created_byNoCreator user object
propertiesNoDatabase properties and their configurations
descriptionNoDatabase description content blocks
created_timeNoISO 8601 creation timestamp
last_edited_byNoLast editor user object
last_edited_timeNoISO 8601 last edit timestamp

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds mild context about return content but no additional behavioral traits like error handling or rate limits.

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?

Single sentence, front-loaded key action, no wasted words.

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

Completeness5/5

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

With one parameter, rich annotations, and output schema present, the description sufficiently explains the tool's purpose and return content without gaps.

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%, so the schema already documents the only parameter. The description adds no new parameter meaning beyond 'by ID'.

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?

Describes a specific verb and resource ('Get Notion database schema by ID'), clearly distinguishing it from sibling tools like notion_query_database by focusing on schema, properties, field types, and configuration.

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?

Implies usage for understanding database structure, but does not explicitly state when to avoid or mention alternatives. Still clear enough given the tool name and context.

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

All Notion_connect toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Several tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route questions to the same 5,708 tools, with beta explicitly described as currently identical to the stable version. Prediction-market tools (bet_research, polymarket_edges, polymarket_arbitrage) also blur together, and the Notion tools are a small island in a sea of unrelated Pipeworx utilities.

Naming Consistency3/5

The names are uniformly lowercase with underscores, but conventions are mixed: some use verb-first patterns (ask_pipeworx, generate_llms_txt, scan_dependency), others are noun-phrases (entity_profile, recent_changes, polymarket_edges), and domain prefixes are inconsistent (notion_*, polymarket_*, pipeworx_*, but bare bet_research, compare_entities, recall). It is readable but lacks a coherent naming scheme.

Tool Count2/5

36 tools is already heavy, but the bigger issue is scope: the server is named Notion_connect yet only 5 of 36 tools relate to Notion. The rest span data research, prediction markets, memory, subscriptions, AI visibility, npm auditing, and llms.txt generation — a grab bag far beyond any single purpose, with multiple redundant meta-tools inflating the count.

Completeness2/5

As a Notion connector it is severely incomplete: there is no create/update/delete for pages or databases, and no way to write content back to Notion — only read/search/query operations. For the broader Pipeworx surface, the tool set is sprawling but unfocused, so it is hard to identify a coherent domain where coverage could be considered complete.

Resources