Skip to main content
Glama

mcp-notion__notion-get-tool-access

Read-onlyIdempotent

Inspect current tool availability, parameter restrictions, and recovery links when diagnosing an access problem or when the user asks about access. For routine work, call the tool you need directly; no access precheck is required. Tool results report access denials and recovery steps for the calling account. Call with {} for the full access map, or pass tool_names, for example ["search", "connector_search"], to narrow the result. Reuse access information already in context, but the operation's result is authoritative if access changes. Use tools marked "available". Use tools marked "available_with_limit" within their limits. It shows one of two content-search setups. Unified search: use ai_search when it is available, including user lookup with query_type="user", and search is then omitted; otherwise use search. Split search: ai_search is omitted, search covers Notion pages, databases, and user lookup, and connector_search covers connected sources such as Slack or Google Drive. connector_search needs AI sear… 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-tool-access"
  }
}

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)
tool_namesNoOptional RunTool names to include, such as search and ai_search. Omit to return all tools visible to this connection. Unknown or unexposed names are omitted. An empty list returns an empty map.
instructions_versionNoNotion setup instructions version, such as 0.0.2. Omit if unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: results carry access denials and recovery steps for the calling account, and are authoritative when access changes mid-session. It loses a point for the garbled trailing fragment about "connector_search needs AI sear…" and the awkward aside about the server marking it read-only.

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 opening sentences are well front-loaded, but the passage then drifts into a long explanation of unified vs. split content-search setups that belongs more to ai_search/search than to an access inspection tool. The description is also visibly truncated mid-word, which hurts readability and trust.

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 introspection tool with no output schema, the description does the needed work: what it returns, how to scope it, and how to interpret the statuses. The only real gap is that the return shape (a map keyed by tool name) is implied rather than stated, and the truncated search section is incomplete.

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 every parameter including skill, site_id, and instructions_version is already documented there. The description reinforces tool_names with a concrete example and shows that {} yields the full map, but adds no semantics the schema lacks. Baseline 3 is appropriate.

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: "Inspect current tool availability, parameter restrictions, and recovery links". It also distinguishes itself from the rest of the catalog by saying it is a diagnostic rather than a work tool, which an agent can act on without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ("when diagnosing an access problem or when the user asks about access") and an explicit counter-case ("For routine work, call the tool you need directly; no access precheck is required"). It also tells the agent how to consume the result (use "available"; respect "available_with_limit") and to prefer stale context only until access changes.

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