Skip to main content
Glama
Sign In

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), notes (what the user wrote or asked noticed to remember), and memories (what noticed worked out on its own). scope:'team' opens the POOLED TEAM record for a person from a team search_people hit, combined across every team you're in — who on your teams knows them + their strength, and full-consent teammates' actions/notes/interactions attributed to each member and tagged with the teams that share them. For someone in your own network, the team section adds the same teammate context (absent when no teammate knows them). 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

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' — one team's team_id (from account_status.teams) to read only that team's record. Omit it to combine the record across every team you're in.
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 from your own network — adds a shared_signals section. Ignored for scope:'team' records.

Output 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. Changed1 schema field changed
    • changedInput schema / properties / team_id / description
      Previous value: -"For scope:'team' — the team_id from account_status.teams. Optional when you're in exactly one team; required otherwise."New value: +"For scope:'team' — one team's team_id (from account_status.teams) to read only that team's record. Omit it to combine the record across every team you're in."
  2. Changed2 schema fields changed
    • changedInput schema / properties / compared_to / description
      Previous value: -"Optional second person_id — adds a shared_signals section."New value: +"Optional second person_id from your own network — adds a shared_signals section. Ignored for scope:'team' records."
    • changedInput schema / properties / team_id / description
      Previous value: -"For scope:'team' — the organizationId (from account_status.teams). Optional when you're in exactly one team; required otherwise."New value: +"For scope:'team' — the team_id from account_status.teams. Optional when you're in exactly one team; required otherwise."
  3. 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"
+}
  4. 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"
+}
  5. 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"
+}
  6. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only cover safety (readOnly, idempotent, non-destructive) and closed-world; the description goes well beyond them, disclosing the default versus 'extras' payload split, that legacy collections preview up to 12 items, that cursors/limit are needed for complete reads, that section metadata distinguishes missing/unrequested/failed, and that an empty field means not recorded rather than false. It also explains team pooling and consent attribution and which consenting teammates' data is merged.

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?

It is front-loaded with what the default read returns, which is good, but the body runs long and spends many sentences documenting individual output fields (contact, relationship, memories, relationship_type_evidence) that an existing output schema already carries. That bulk makes it harder to scan for the actionable decisions: which scope, which include, how to page.

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, nested read with team pooling, sectioned paging and an output schema, the description covers defaults, paging behavior, empty-value semantics and scope semantics. Nothing material needed to call it correctly 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?

Schema coverage is 100%, so a 3 is the baseline, but the description adds meaning the schema does not: compared_to is resolved against 'current canonical values', the team scope is pooled across every team unless team_id narrows it, and it warns to read contact.emails rather than the single top-level email. The include:'extras' restatement largely duplicates the schema, keeping this below a 5.

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 opens with a specific resource and its scope: 'One person's unified knowledge and compact legacy record', then enumerates the default payload (profile, current role, relationship context). It implicitly distinguishes itself from search_people by naming it as the source of person_id and from list-style siblings by emphasizing a single-person read. It stops short of a crisp verb-first statement and never explicitly contrasts with my_profile or resolve_person.

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?

Routing conditions are given for the main branches: person_id:'me' for yourself, scope:'team' only for a person from a team search_people hit, include:'extras'/'all' for work history, and compared_to ignored for team records. It does not state when NOT to use this tool or name an alternative for the same task (e.g., my_profile, research_person), so exclusions are absent.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources