Skip to main content
Glama

mcp-notion__notion-get-enabled-skills

Read-onlyIdempotent

Use this tool to view the Notion skills the user has enabled for you and other external MCP clients, each with a name and a description of when it should be used. If you choose to use one of these skills, mention to the user that you are loading the skill from Notion first, then download them. 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-enabled-skills"
  }
}

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

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the sentence 'its server marks it read-only, so it runs straight away' simply restates them rather than adding new behavior. The one genuinely additive detail is the interaction norm — tell the user you are loading a skill from Notion before downloading — which is useful behavioral context beyond the schema, though the surrounding 'Through Royally:' phrasing reads as gateway noise.

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 core purpose is front-loaded in the first sentence, but the trailing 'Through Royally: its server marks it read-only, so it runs straight away' is artifact text that duplicates annotations and consumes attention without adding information. The middle sentence is useful but could be tighter.

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 read-only, zero-required-parameter listing tool with no output schema, the description covers what is returned (skill names plus usage descriptions) and what to do next (announce, then download). Nothing essential to invoking it correctly is missing, though the handoff to the download tool could be made explicit.

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 three parameters (skill, site_id, instructions_version) are already explained in the schema as tracking metadata. The description adds no parameter-level meaning, which is acceptable at this coverage level but earns only the baseline.

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 uses a specific verb and resource ('view the Notion skills the user has enabled') and even characterizes the returned shape (each skill has a name and a description of when to use it). It stops short of naming the companion tool by name, but the phrase 'then download them' points clearly toward the download-skill sibling, so an agent can distinguish this listing step from the fetching step.

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?

It gives a clear trigger ('Use this tool to view the Notion skills the user has enabled') and an implied follow-on workflow (mention the load to the user, then download). There is no explicit when-not guidance and no named alternative, so an agent must infer the sequencing from 'then download them' rather than being routed by tool name.

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