Skip to main content
Glama

mcp-notion__notion-wait-session

Read-only

Wait for the latest turn in a Custom Agent session to stop running.

Requires Notion AI and Custom Agents access. Call this tool directly. If access is denied, follow the recovery guidance in the result. Through Royally: its server marks it read-only, so it runs straight away.

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": {
      "session_url": "<session_url>",
      "seconds": "<seconds>"
    },
    "name": "mcp-notion__notion-wait-session"
  }
}

Input Schema

NameRequiredDescriptionDefault
skillNoFor tracking only: the name of the agent skill you are following for this task, such as notion-meeting-prep. Omit if you are not following a skill.
secondsYesMaximum number of seconds to wait.
site_idNoSite to run this tool on: ded71e55-0da4-4a52-8f14-1224fa9979b9 (https://mcp.notion.com/mcp)
session_urlYesUse the complete session_url returned by session tools, unchanged. Format: session://<spaceId>/<sessionId>. Shorthand session://<sessionId> and thread://<sessionId> use the connected workspace. Fully qualified URLs must refer to that workspace.
instructions_versionNoNotion setup instructions version, such as 0.0.2. Omit if unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds context the annotations cannot: an access prerequisite, a documented failure mode with recovery instruction, and a note that the server treats it as read-only so no approval round-trip occurs. It does not say what the return payload looks like or whether a timeout returns partial state, which keeps it at 4.

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 core action is front-loaded in the first sentence and the remaining sentences carry prerequisites and error handling without padding. The phrasing around the read-only note ('Through Royally: its server marks it read-only, so it runs straight away') is slightly awkward but still earns its place by explaining why the call is not gated.

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 five-parameter tool with a fully documented schema, no output schema, and full annotation coverage, the description supplies the missing pieces an agent needs: access requirement, blocking semantics, direct-invocation instruction, and denied-access recovery. Only the timeout/return behavior is unaddressed.

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 session_url format, seconds bounds (1-60), site_id enum, and the optional tracking fields all documented in the schema itself. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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?

The description opens with a specific verb and resource: 'Wait for the latest turn in a Custom Agent session to stop running.' That makes the blocking/polling nature clear and distinguishes it in spirit from status/listing siblings like get-session-status or list-session-events. It stops short of naming an alternative, so a 4 rather than a 5.

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 real operational guidance: 'Call this tool directly', a prerequisite ('Requires Notion AI and Custom Agents access'), and a fallback ('If access is denied, follow the recovery guidance in the result'). What it lacks is an explicit comparison against sibling session tools, so an agent must infer when waiting beats polling status.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources