Skip to main content
Glama
Sign In

noticed

by so.noticed.mcp
OverviewDiscussionsAdmin

enrich_person

Idempotent

Enrich a person in your noticed network with missing or updated professional details.

Input Schema

NameRequiredDescriptionDefault
scopeNoUse team for a fully shared Team relationship.
team_idNoTeam id; required when you belong to multiple Teams.
batch_idNoOpportunity List id for resumable enrichment.
person_idNoAn existing noticed person to enrich.
new_personNoCreate a new own-network relationship before enrichment. Requires email or linkedin_url; not allowed with scope 'team'. Pass exactly one of person_id or new_person.
client_request_idNoStable idempotency key for creating a new relationship.
confirmation_tokenNoOnly from a needs_duplicate_confirmation response for new_person: pass it back to create the relationship despite the listed potential duplicates.

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. Changed2 schema fields changed
    • addedInput schema / properties / confirmation_token / description
      Added value: +"Only from a needs_duplicate_confirmation response for new_person: pass it back to create the relationship despite the listed potential duplicates."
    • changedInput schema / properties / new_person / description
      Previous value: -"Create a new own-network relationship before enrichment."New value: +"Create a new own-network relationship before enrichment. Requires email or linkedin_url; not allowed with scope 'team'. Pass exactly one of person_id or new_person."
  2. Changed3 schema fields changed
    • changedInput schema / properties / client_request_id / description
      Previous value: -"Stable idempotency key; required for name-only new-person research."New value: +"Stable idempotency key for creating a new relationship."
    • removedInput schema / properties / mode
      Removed value: -{
-  "description": "Fast is the default deterministic lookup; research starts a live agent-led search session.",
-  "enum": [
-    "fast",
-    "research"
-  ],
-  "type": "string"
-}
    • changedOutput schema / properties / data / properties / status / enum
      Previous value: -[
-  "started",
-  "in_progress",
-  "recently_enriched",
-  "not_eligible",
-  "needs_duplicate_confirmation",
-  "research_required"
-]New value: +[
+  "started",
+  "in_progress",
+  "recently_enriched",
+  "not_eligible",
+  "needs_duplicate_confirmation"
+]
  3. Changed12 schema fields changed
    • addedInput schema / properties / batch_id
      Added value: +{
+  "description": "Opportunity List id for resumable enrichment.",
+  "format": "uuid",
+  "type": "string"
+}
    • addedInput schema / properties / client_request_id
      Added value: +{
+  "description": "Stable idempotency key; required for name-only new-person research.",
+  "format": "uuid",
+  "type": "string"
+}
    • addedInput schema / properties / confirmation_token
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / mode
      Added value: +{
+  "description": "Fast is the default deterministic lookup; research starts a live agent-led search session.",
+  "enum": [
+    "fast",
+    "research"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / new_person
      Added value: +{
+  "additionalProperties": false,
+  "description": "Create a new own-network relationship before enrichment.",
+  "properties": {
+    "email": {
+      "format": "email",
+      "type": "string"
+    },
+    "linkedin_url": {
+      "format": "uri",
+      "type": "string"
+    },
+    "name": {
+      "minLength": 2,
+      "type": "string"
+    }
+  },
+  "required": [
+    "name"
+  ],
+  "type": "object"
+}
    • changedInput schema / properties / person_id / description
      Previous value: -"The noticed person to enrich."New value: +"An existing noticed person to enrich."
    • addedInput schema / properties / scope
      Added value: +{
+  "description": "Use team for a fully shared Team relationship.",
+  "enum": [
+    "own",
+    "team"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / team_id
      Added value: +{
+  "description": "Team id; required when you belong to multiple Teams.",
+  "format": "uuid",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "person_id"
-]
    • addedOutput schema / properties / data / properties / reason
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / properties / data / properties / status / enum
      Previous value: -[
-  "started",
-  "in_progress",
-  "recently_enriched",
-  "not_eligible"
-]New value: +[
+  "started",
+  "in_progress",
+  "recently_enriched",
+  "not_eligible",
+  "needs_duplicate_confirmation",
+  "research_required"
+]
    • changedOutput schema / properties / data / required
      Previous value: -[
-  "status",
-  "person_id",
-  "available"
-]New value: +[
+  "status"
+]
  4. Added

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already state this is a non-read-only, non-destructive, idempotent operation, and the description's 'missing or updated details' is consistent with that safety profile. However, it does not disclose key behaviors visible in the schema: creating a new relationship via new_person, duplicate confirmation handling, or resumable batch enrichment.

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 definition is a single front-loaded sentence with no filler. It states the action and target immediately, though its brevity contributes to gaps elsewhere.

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

Completeness3/5

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

For a tool with seven parameters, nested new_person input, team scoping, duplicate confirmation, and batch resumability, the description is quite thin. The rich schema and output schema mitigate this, but the description still does not help an agent distinguish this operation from update_person or understand its creation side effect.

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 description coverage is 100%, so parameter meanings are already well documented in the input schema. The description adds no parameter-specific meaning beyond the schema, which is appropriate but not value-adding for this dimension.

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 gives a specific verb ('Enrich') and resource ('a person in your noticed network') and narrows the outcome to missing or updated professional details. It is understandable without opening the schema, though it does not explicitly distinguish itself from siblings like update_person or research_person.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance or comparison to alternatives such as update_person, research_person, or add_to_network. The phrase 'in your noticed network' implies an existing relationship, but the agent is left to infer when enrichment is the right choice.

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