Skip to main content
Glama

mcp-notion__notion-get-setup-guide

Read-onlyIdempotent

Returns Notion's setup guide for agents: how to set up Notion as the user's shared context and memory across agents. Call it when the user asks you to set up Notion or the Notion MCP, then follow the guide step by step with the user. Through Royally: its server marks it read-only, so it runs straight away.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mcp-notion__notion-get-setup-guide"
  }
}

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.
site_idNoSite to run this tool on: ded71e55-0da4-4a52-8f14-1224fa9979b9 (https://mcp.notion.com/mcp)
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
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description's 'its server marks it read-only, so it runs straight away' largely restates that rather than adding new behavioral detail. The genuinely additive part is procedural: the agent is told to walk the user through the guide step by step. Nothing is said about what the guide contains or how it should be presented/verified.

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?

Three short sentences, front-loaded with what the tool returns and then the trigger condition. The 'Through Royally' sentence is awkward and mostly duplicates annotation data, but the overall text is tight and free of filler.

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?

A simple read-only, zero-required-parameter tool with no output schema, so the description needn't explain return values. It covers purpose, trigger, and the expected follow-up actions, leaving only minor gaps about the guide's shape.

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 coverage is 100%, so all three optional parameters (skill, site_id, instructions_version) are already documented in the schema with their purpose and defaults. The description adds no meaning beyond that, so the 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?

States a specific verb and resource ('Returns Notion's setup guide for agents') and scopes its content ('how to set up Notion as the user's shared context and memory across agents'). An agent can immediately tell this apart from retrieval tools like notion-fetch or notion-search.

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?

Gives a clear trigger condition: 'Call it when the user asks you to set up Notion or the Notion MCP,' plus the follow-up behavior ('follow the guide step by step with the user'). It doesn't name alternatives or say when not to call it, which keeps it at 4 rather than 5.

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