Skip to main content
Glama

noticed

by so.noticed.mcp
OverviewDiscussionsAdmin

my_profile

Read-onlyIdempotent

Your complete permission-aware self knowledge, including onboarding research before external accounts are connected. Shares canonical claims, citations and versions with get_person('me'). Legacy fields are compact previews; request sections and use cursors for full histories and explicit completeness/indexing state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum items per requested section, default 10. Follow nextCursor to retrieve the rest.
cursorsNoPer-section nextCursor values from the previous read; restart a section when its source version changes.
sectionsNoKnowledge sections to read. Each returns a bounded page, completeness state and continuation cursor.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether noticed completed the operation.
dataNoThe operation result when ok is true.
errorNoA human-readable error when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / cursors
      Added value: +{
+  "additionalProperties": {
+    "maxLength": 2000,
+    "type": "string"
+  },
+  "description": "Per-section nextCursor values from the previous read; restart a section when its source version changes.",
+  "propertyNames": {
+    "enum": [
+      "identity",
+      "background",
+      "work",
+      "recognition",
+      "direction",
+      "relationships",
+      "notes",
+      "actions",
+      "timeline",
+      "research"
+    ]
+  },
+  "type": "object"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Maximum items per requested section, default 10. Follow nextCursor to retrieve the rest.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / sections
      Added value: +{
+  "description": "Knowledge sections to read. Each returns a bounded page, completeness state and continuation cursor.",
+  "items": {
+    "enum": [
+      "identity",
+      "background",
+      "work",
+      "recognition",
+      "direction",
+      "relationships",
+      "notes",
+      "actions",
+      "timeline",
+      "research"
+    ],
+    "type": "string"
+  },
+  "maxItems": 10,
+  "type": "array"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "data": {
+      "additionalProperties": true,
+      "description": "The operation result when ok is true.",
+      "properties": {},
+      "type": "object"
+    },
+    "error": {
+      "description": "A human-readable error when ok is false.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether noticed completed the operation.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, not open-world), so the bar is lower. The description adds real behavioral context beyond them: permission-aware scoping, inclusion of onboarding research gathered before external accounts were connected, legacy fields being compact previews, and explicit completeness/indexing state with cursors.

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

Conciseness4/5

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

Three tight sentences, front-loaded with the primary purpose and the get_person relationship. The section/cursor mechanics come second. Minor jargon ('completeness/indexing state') costs a little clarity but no sentence is filler.

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?

An output schema exists, so return values need no explanation here. Given the nested object params (per-section cursors keyed by section name) and the 100% schema coverage, the description supplies the missing conceptual layer — why sections and cursors matter for completeness — making it adequate for invocation.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: legacy fields are previews only, sections must be requested to get full histories, and cursors surface explicit completeness/indexing state. This clarifies why the parameters exist rather than restating their types.

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 identifies the resource precisely as the caller's own profile ('Your complete permission-aware self knowledge') and names the related sibling get_person('me'), noting they share canonical claims. The verb is implicit (read) rather than stated, but an agent can tell what it retrieves and how it relates to get_person.

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 procedural guidance ('request sections and use cursors for full histories') but never states when to choose my_profile over get_person('me') or any other sibling, nor any exclusions. Usage is implied by the data-relationship note rather than spelled out as a routing rule.

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

All noticed toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources