noticed

list_intros

Read-onlyIdempotent

The user's pending introductions — who offered, who they'll be connected to, and where each stands (waiting/ready/requested/done/dropped). Answers "what intros am I waiting on?" and "who promised to connect me to someone?".

Input Schema

Name	Required	Description
`limit`	No	Max rows (default 50, max 200).
`status`	No	Filter by lifecycle status.
`connector_person_id`	No	Only intros offered by this person.

Output Schema

Name	Required	Description
`ok`	Yes	Whether noticed completed the operation.
`data`	No	The operation result when ok is true.
`error`	No	A human-readable error when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026
- changedInput schema / properties / limit / description
```
Previous value: -"Max rows (default 50)."New value: +"Max rows (default 50, max 200)."
```

Changed1 schema field changedAug 22, 2026

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": {
+        "intros": {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "connector_name": {
+                "type": "string"
+              },
+              "connector_person_id": {
+                "type": "string"
+              },
+              "id": {
+                "type": "string"
+              },
+              "notes": {
+                "$ref": "#/properties/data/properties/intros/items/properties/target_org"
+              },
+              "resolved_person_id": {
+                "$ref": "#/properties/data/properties/intros/items/properties/target_org"
+              },
+              "status": {
+                "type": "string"
+              },
+              "target_name": {
+                "type": "string"
+              },
+              "target_org": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "total": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "intros",
+        "total"
+      ],
+      "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"
+}

First observedAug 22, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds scope ('the user's') and the lifecycle vocabulary, but says nothing about ordering, pagination default behavior, or whether 'pending' really means all five statuses — a title/description tension worth flagging.

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?

Two sentences, front-loaded with the resource and its scope, followed by the questions it answers. The parenthetical status list is mild duplication of the schema enum but is cheap and readable.

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?

With an output schema, full parameter coverage, and strong read-only annotations, the definition supplies most of what an agent needs. The remaining gap is the missing link to track_intro and the slight ambiguity between 'pending' and a status filter that includes done/dropped.

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 all three parameters are documented in the schema itself; baseline 3 applies. The description only echoes the status vocabulary already in the enum and adds no meaning for connector_person_id or the limit behavior.

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 names a specific resource (the user's introductions) and enumerates what each row carries — who offered, who the connection is to, and lifecycle status. An agent can tell this is a read/list tool, though it never names the natural sibling (track_intro) to distinguish listing from creating/tracking an intro.

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?

Usage is conveyed only indirectly, through the example questions ('what intros am I waiting on?', 'who promised to connect me to someone?'), which imply the right context. There is no explicit when-not guidance and no mention of track_intro as the alternative for creating or advancing an intro.

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

All noticed tools Inspect

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

Need Help?