Skip to main content
Glama
Sign In

QuestionPunk

by io.github.questionpunk
OverviewDiscussionsAdmin

Notion List Databases

notion_list_databases
Read-onlyIdempotent

Search the Notion databases a connected workspace shared with QuestionPunk, to send a survey's responses into one that exists. Returns { databases: [{ dataSourceId, databaseId, title, icon, url }] }; pass dataSourceId to notion_survey_link_database. A database the user expects but that is missing was not shared with QuestionPunk in Notion.

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": {
      "connectionId": "<connectionId>"
    },
    "name": "notion_list_databases"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoWords in the title; leave out to list the most recently edited
connectionIdYesA connected workspace's id (connections[].id from notion_status)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare this is read-only, open-world, idempotent, and non-destructive, so the description adds useful context beyond safety: it explains the returned identifier handoff and clarifies that an expected missing database was not shared with QuestionPunk. It does not discuss pagination or rate limits, but the schema covers the main query behavior.

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 compact and front-loaded with the action, scope, and purpose. The return shape and dataSourceId handoff are stated efficiently, and the missing-database caveat is included without excess wording.

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?

For a read-only lookup tool with a complete schema and an output schema, this description is sufficiently complete. It covers the purpose, the key returned identifier, the follow-up call, and the common failure case where a database was not shared.

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 input meanings are already documented. The description reinforces the output field dataSourceId for the follow-up tool, but it does not add input-parameter semantics beyond what the schema provides.

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 states a specific verb and resource: searching Notion databases shared with QuestionPunk in a connected workspace. It distinguishes this from listing pages and from creating databases by framing it as finding one that already exists to link survey responses.

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: find an existing Notion database to receive a survey's responses, then pass the returned dataSourceId to notion_survey_link_database. It does not mention the alternative of notion_survey_create_database when no suitable database exists, so the when-not guidance is incomplete.

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

All QuestionPunk 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