Skip to main content
Glama
Sign In

QuestionPunk

by io.github.questionpunk
OverviewDiscussionsAdmin

Notion Survey Sync Get

notion_survey_sync_get
Read-onlyIdempotent

Read a survey's Notion sync: the workspace and database (with its Notion url), whether it is on, what each page includes, counts of responses synced, failed and not yet synced, the last error code, questions with no column, and whether a backfill is running. Returns { isOwner, sync }; sync is null when the survey is not syncing. Only the survey's owner can sync it (isOwner false otherwise).

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": {
      "surveyId": "<surveyId>"
    },
    "name": "notion_survey_sync_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
surveyIdYesThe survey ID (from survey_list)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the supplied annotations (readOnly, idempotent, non-destructive), the description discloses two non-obvious behaviors: sync is null when the survey isn't syncing, and isOwner is false for non-owners because only the owner can sync. Those are exactly the kind of edge cases an agent would otherwise have to discover at runtime.

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

Conciseness3/5

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

The verb and resource are front-loaded, which is good, but the long mid-sentence enumeration of returned fields overlaps heavily with the output schema, which already exists. That field list consumes most of the description without adding much beyond what structured data provides, though the final two clauses about null sync and ownership do earn their place.

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 single-parameter, read-only tool with an output schema and full annotation coverage, the description covers the essentials: what is read, the null-sync case, and the ownership gate. It is slightly over-specified on return fields that the output schema already documents, but nothing an agent needs to invoke it correctly is missing.

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?

Only one parameter exists and schema coverage is 100%, with the schema itself noting it comes from survey_list. The description adds no format, constraint, or sourcing detail beyond that, so the baseline of 3 applies rather than a higher score.

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?

Opens with a specific verb and resource ('Read a survey's Notion sync') and scopes it precisely to a single survey's sync configuration, which is easy to distinguish from the write-side siblings like notion_survey_sync_start and notion_survey_link_database. It stops short of naming those siblings explicitly, so differentiation is inferred from the verb rather than stated.

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

Usage Guidelines3/5

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

There is no explicit statement of when to call this versus notion_status, notion_list_databases, or notion_survey_sync_start, only the implied context of inspecting an existing sync. The owner-only note is a precondition rather than a use-case routing rule, so guidance remains inferred.

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