Skip to main content
Glama

noticed

by so.noticed.mcp
OverviewDiscussionsAdmin

get_person

Read-onlyIdempotent

One person's unified knowledge and compact legacy record: profile (including github_login and github_url when known; team records use githubHandle and githubUrl), current role, and your relationship context (notes, tags, last interaction, added_at = when they entered your network) by default; pass include:'extras' or 'all' for work history, education, and repos. person_id:'me' for yourself. The contact section previews their emails, phones, and companies (primary first) — a person can have several of each, so read contact.emails rather than the single top-level email when the user asks for their addresses. The relationship section carries your memory of them: summary (cited), strength ({score, category}), mutuals (shared connections), actions (follow-ups — done flags completion), and memories (saved notes). scope:'team' opens the POOLED TEAM record for a person from a team search_people hit — who on the team knows them + their strength, and full-consent teammates' actions/notes/interactions attributed to each member. Relationship types include manual/derived origin, persistent rejections, and relationship_type_evidence with shared company/university, both date ranges, overlap precision, and provenance. Legacy collections preview up to 12 items; use sections, cursors and limit for complete authorized knowledge and source histories. compared_to uses current canonical values. Section metadata distinguishes missing, unrequested and failed reads. An empty field means not recorded, NOT false.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum items per requested section, default 10. Follow nextCursor to retrieve the rest.
scopeNo'own' (default) — your own record. 'team' — the pooled TEAM record for a person from a team search_people hit (who knows them + full-consent teammates' notes/actions/interactions).
cursorsNoPer-section nextCursor values from the previous read; restart a section when its source version changes.
includeNo'dossier' (default, fast) · 'extras' (work history/education/repos) · 'all'.
team_idNoFor scope:'team' — the organizationId (from account_status.teams). Optional when you're in exactly one team; required otherwise.
sectionsNoKnowledge sections to read. Each returns a bounded page, completeness state and continuation cursor.
person_idYesThe person's id (from search_people), or the literal 'me' for yourself.
compared_toNoOptional second person_id — adds a shared_signals section.

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. Changed3 schema fields changed
    • 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
    • addedOutput schema / properties / data / properties / enrichment
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "available": {
+      "type": "boolean"
+    },
+    "next_enrichment_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "enum": [
+        "available",
+        "pro_team_required",
+        "not_found",
+        "no_email",
+        "in_progress",
+        "recently_enriched"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "available",
+    "status",
+    "next_enrichment_at"
+  ],
+  "type": "object"
+}
  3. 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": {
+        "compared_to": {
+          "$ref": "#/properties/data/properties/person"
+        },
+        "contact": {
+          "$ref": "#/properties/data/properties/person"
+        },
+        "person": {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        "relationship": {
+          "$ref": "#/properties/data/properties/person"
+        },
+        "scope": {
+          "enum": [
+            "own",
+            "team",
+            "public"
+          ],
+          "type": "string"
+        },
+        "shared_signals": {
+          "$ref": "#/properties/data/properties/person"
+        },
+        "team": {
+          "$ref": "#/properties/data/properties/person"
+        }
+      },
+      "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"
+}
  4. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, but the description adds substantial semantics beyond them: empty means not recorded (NOT false), section metadata distinguishes missing vs unrequested vs failed reads, legacy collections preview up to 12 items with cursors/limit for full reads, and team scope attributes notes/actions/interactions to individual members. These are exactly the return-state and scoping behaviors an agent needs.

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 core purpose is front-loaded, but the body is one sprawling, semicolon-chained paragraph that mixes purpose, parameter guidance, and return-value semantics. Most sentences carry real information, yet the density and lack of structural separation make it hard to scan.

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 an 8-parameter tool with nested objects and an output schema, the description is complete: it covers default vs extended reads, team pooling, comparison mode, pagination, and failure-state signaling. Nothing needed to invoke it correctly is missing.

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 the baseline is 3; nearly all parameter meaning (include, scope, person_id, compared_to, team_id, sections, cursors, limit) is already documented in the schema descriptions. The description largely restates those enum semantics rather than adding new syntax or format detail, with only minor cross-parameter context added.

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 opening clause states the resource precisely ("One person's unified knowledge and compact legacy record") and enumerates its default contents, so an agent knows this opens a full person record. It distinguishes itself from search_people by naming it as the id source and from my_profile via person_id:'me'. The verb is implicit rather than stated, keeping it short of a 5.

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?

Gives concrete when-to conditions for options: include:'extras'/'all' for work history/education/repos, scope:'team' when the person came from a team search_people hit, person_id:'me' for yourself, and compared_to for a diff. It also instructs reading contact.emails over the top-level email when the user asks for addresses. No explicit when-not or named alternative tools, so not a 5.

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