notipo

Get Settings

get_settings

Read-only

Retrieve your Notipo account configuration, including connected services (like Notion and WordPress), current plan, feature settings, and trigger statuses.

Instructions

Get your Notipo account configuration: which services are connected (Notion, WordPress), current plan, feature settings, and trigger statuses.

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": "get_settings"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`plan`	Yes	FREE \| TRIAL \| PRO
`wpSeoPlugin`	Yes	Detected SEO plugin: RANK_MATH \| YOAST \| SEOPRESS \| AIOSEO
`codeHighlighter`	Yes
`notionConnected`	Yes
`wordpressConnected`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.2.4Jul 4, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "codeHighlighter": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "notionConnected": {
+      "type": "boolean"
+    },
+    "plan": {
+      "description": "FREE | TRIAL | PRO",
+      "type": "string"
+    },
+    "wordpressConnected": {
+      "type": "boolean"
+    },
+    "wpSeoPlugin": {
+      "description": "Detected SEO plugin: RANK_MATH | YOAST | SEOPRESS | AIOSEO",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "notionConnected",
+    "wordpressConnected",
+    "plan",
+    "wpSeoPlugin",
+    "codeHighlighter"
+  ],
+  "type": "object"
+}

First observedv0.1.0Jun 23, 2026

TDQS

A4.3/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 description adds useful context about the specific content returned (services, plan, features, triggers). No behavioral traits beyond annotations are disclosed, but the added value is solid.

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 a single, well-structured sentence that front-loads the purpose and lists specifics. Every word contributes meaning without redundancy.

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

Completeness5/5

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

Given the tool has no parameters, has an output schema, and annotations indicate safety, the description fully covers what the tool does and returns. No gaps remain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has no parameters, so the description naturally cannot add parameter info. Baseline for zero parameters is 4, and no further compensation is needed.

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?

The description clearly states the tool retrieves account configuration, specifying exactly what it includes (connected services, plan, features, triggers). This distinctively separates it from sibling tools like get_post or list_posts.

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?

The description implies usage for viewing settings but does not provide explicit when-to-use or when-not-to-use guidance compared to alternatives. No comparison with siblings is made.

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

Deploy Server