Skip to main content
Glama

NotePom

by com.notepom

NotePom capabilities

get_notepom_capabilities
Read-onlyIdempotent

Call this first. Discover NotePom as persistent workspace memory, inspect the current autonomous-agent signup mode, and receive the safe bootstrap sequence.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolsYes
limitsYes
safetyYes
scopesYes
serverYes
purposeYes
versionYes
protocolYes
resourceYes
agentSignupYes
marketplaceYes
authenticationYes
bootstrapStepsYes
memoryGuidanceYes
accountLifecycleYes
visualCompositionYes
workspaceBootstrapYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / accountLifecycle
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "agentOnly": {
+      "const": true,
+      "type": "boolean"
+    },
+    "confirmation": {
+      "const": "DELETE MY NOTEPOM AGENT ACCOUNT",
+      "type": "string"
+    },
+    "deletesWorkspace": {
+      "const": true,
+      "type": "boolean"
+    },
+    "permanent": {
+      "const": true,
+      "type": "boolean"
+    },
+    "requiresExplicitHumanRequest": {
+      "const": true,
+      "type": "boolean"
+    },
+    "revokesAllCredentials": {
+      "const": true,
+      "type": "boolean"
+    },
+    "selfDeletionTool": {
+      "const": "delete_own_agent_account",
+      "type": "string"
+    }
+  },
+  "required": [
+    "selfDeletionTool",
+    "agentOnly",
+    "permanent",
+    "requiresExplicitHumanRequest",
+    "confirmation",
+    "revokesAllCredentials",
+    "deletesWorkspace"
+  ],
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "protocol",
-  "version",
-  "server",
-  "resource",
-  "purpose",
-  "agentSignup",
-  "authentication",
-  "workspaceBootstrap",
-  "bootstrapSteps",
-  "memoryGuidance",
-  "visualComposition",
-  "scopes",
-  "tools",
-  "limits",
-  "marketplace",
-  "safety"
-]New value: +[
+  "protocol",
+  "version",
+  "server",
+  "resource",
+  "purpose",
+  "agentSignup",
+  "authentication",
+  "workspaceBootstrap",
+  "accountLifecycle",
+  "bootstrapSteps",
+  "memoryGuidance",
+  "visualComposition",
+  "scopes",
+  "tools",
+  "limits",
+  "marketplace",
+  "safety"
+]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / visualComposition
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "base64InMarkdownAllowed": {
+      "const": false,
+      "type": "boolean"
+    },
+    "documentModel": {
+      "const": "pretext",
+      "type": "string"
+    },
+    "guidance": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "mediaWorkflow": {
+      "items": [
+        {
+          "const": "upload_file",
+          "type": "string"
+        },
+        {
+          "const": "upsert_note.media",
+          "type": "string"
+        }
+      ],
+      "maxItems": 2,
+      "minItems": 2,
+      "type": "array"
+    },
+    "styledBlocksField": {
+      "const": "pretextBlocks",
+      "type": "string"
+    },
+    "supports": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "textAnimations": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "writeTool": {
+      "const": "upsert_note",
+      "type": "string"
+    }
+  },
+  "required": [
+    "documentModel",
+    "writeTool",
+    "styledBlocksField",
+    "mediaWorkflow",
+    "textAnimations",
+    "supports",
+    "base64InMarkdownAllowed",
+    "guidance"
+  ],
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "protocol",
-  "version",
-  "server",
-  "resource",
-  "purpose",
-  "agentSignup",
-  "authentication",
-  "workspaceBootstrap",
-  "bootstrapSteps",
-  "memoryGuidance",
-  "scopes",
-  "tools",
-  "limits",
-  "marketplace",
-  "safety"
-]New value: +[
+  "protocol",
+  "version",
+  "server",
+  "resource",
+  "purpose",
+  "agentSignup",
+  "authentication",
+  "workspaceBootstrap",
+  "bootstrapSteps",
+  "memoryGuidance",
+  "visualComposition",
+  "scopes",
+  "tools",
+  "limits",
+  "marketplace",
+  "safety"
+]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavioral context beyond those annotations: 'persistent workspace memory', 'current autonomous-agent signup mode', and 'safe bootstrap sequence' explain what the agent will discover and receive. This is useful and consistent with the annotations.

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 tightly worded sentence with an upfront imperative. Every clause adds distinct information: sequencing, purpose, memory nature, signup-mode inspection, and bootstrap output. There is no filler or 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?

For a no-parameter capability-discovery tool with an output schema present and safety annotations covering side effects, the description is complete. It tells the agent when to call it, what to expect conceptually, and what it will receive. Nothing critical is missing.

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 zero parameters and the input schema is empty, so parameter semantics are trivial. The description correctly does not attempt to explain nonexistent parameters, and the baseline of 4 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?

The description opens with a clear directive ('Call this first') and states specific capabilities: discovering NotePom as persistent workspace memory, inspecting the autonomous-agent signup mode, and receiving a safe bootstrap sequence. This distinguishes it from the sibling tools, which are all individual operations rather than a capability-discovery bootstrap tool.

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?

The description explicitly says to call this tool first, establishing clear sequencing and bootstrap context. It does not explicitly name alternatives or exclusion conditions, but given this is the discovery/initialization tool among many operational siblings, the usage context is clear enough.

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

All NotePom toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation4/5

Most tools target a distinct resource and action, and lifecycle pairs like publish_note_listing vs publish_media_listing or get_note vs get_collaboration_note are separated by clear wording. A few near-pairs such as move_file vs move_workspace_item and trash_file vs trash_workspace_item could still cause an agent to pick the wrong tool without careful reading.

Naming Consistency5/5

All 38 tools follow one consistent verb_noun snake_case pattern with no camelCase or mixed conventions. Even less common verbs like upsert, trash, purge, and validate are applied uniformly, making the tool set predictable.

Tool Count2/5

38 tools is well above the 25+ threshold and makes the overall surface feel heavy for tool selection. The number is defensible given the broad workspace, collaboration, and marketplace scope, but as a single MCP server it is not especially well-scoped.

Completeness4/5

The tool set covers workspace content lifecycle, collaboration, public pages, marketplace listings, Stripe seller flow, and agent registration without major dead ends. Minor gaps exist, such as no permanent delete outside of the trash flow and no direct collaboration-note deletion, but core workflows are supported.

Resources