Skip to main content
Glama

noticed

by so.noticed.mcp
OverviewDiscussionsAdmin

enrich_person

Idempotent

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoFast is the default deterministic lookup; research starts a live agent-led search session.
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.
client_request_idNoStable idempotency key; required for name-only new-person research.
confirmation_tokenNo

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. 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"
+]
  2. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, idempotent write (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so safety is largely covered. The phrase 'missing or updated' hints that existing data may be modified, which is useful, but the description omits meaningful traits such as creating a brand-new person relationship or launching a live agent-led search session.

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?

A single efficient sentence with the resource and scope front-loaded and no filler. It is terse and readable, though it is arguably too sparse for an 8-parameter tool with a nested object.

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?

An output schema exists and schema coverage is high, so much of the burden is carried elsewhere. However, for a tool with 8 parameters, a nested new_person object, and a batch/research mode, the description omits notable behaviors (creating a new person, resumable batches, the confirmation_token requirement) that an agent should know before invoking.

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 88%, so parameters like mode, scope, team_id, and new_person are already well documented in the schema. The description adds no parameter-level detail (no mention of mode fast vs research, scope, or idempotency), so the baseline of 3 applies.

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?

States a specific verb (enrich) and resource (person) with a scope qualifier ('in your noticed network') and specifies the payload as 'missing or updated professional details.' This is clear enough for an agent to understand the operation, but it does not differentiate itself from siblings like update_person, submit_enrichment_research, or enrichment_batch_status that an agent might otherwise reach for.

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?

The description contains no when-to-use, when-not-to-use, or alternative-tool guidance. It never mentions update_person for manual edits, enrichment_batch_status for tracking, or submit_enrichment_research for research tasks, so the agent must infer routing from the name alone.

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