Skip to main content
Glama

notion_search_intelligent

Destructive

Find relevant Notion content by sending a free-text objective. Optional structured inputs refine the search, and the domain-agent dispatcher routes it under your account scope.

Instructions

Run the notion domain agent action search_intelligent.

Routes through the platform's domain-agent dispatcher under your JWT, tenant, and company scope.

Args: message: Free-text objective for the action. inputs: Optional JSON string of structured inputs for the action.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputsNo{}
messageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

The description mentions routing through a dispatcher and scoping under JWT/tenant/company, but it does not clarify the actual behavior of the search, potential side effects, or return format. The annotations (destructiveHint=true) conflict with the implied non-destructive nature of a search, and the description does not resolve this ambiguity.

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

Conciseness5/5

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

The description is concise and well-structured, with a single clear sentence and a simple parameter list. There is no unnecessary information or verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description gives some context about the dispatcher and scope but does not explain the search's intended use cases, output, or how it relates to sibling tools. While the output schema exists, the description could still provide more operational context for an agent deciding when to invoke it.

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?

Both parameters are described briefly: 'message' is a free-text objective, and 'inputs' is an optional JSON string. This provides basic meaning but lacks details on expected structure, examples, or constraints, leaving the agent to infer the precise format.

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 clearly states the action: 'Run the notion domain agent action `search_intelligent`.' It identifies a specific verb and resource, and the action name implies search functionality. However, it does not explicitly describe what the search does or differentiate it from other Notion tools.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. There is no mention of scenarios where `search_intelligent` is preferred over other Notion or search tools, nor any exclusions.

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

Deploy Server

Other Tools