Skip to main content
Glama
Sign In

noticed

by so.noticed.mcp
OverviewDiscussionsAdmin

network_summary

Read-onlyIdempotent

Lightweight overview of your network — total people, breakdowns by source/company, recent vs stale — without paging through search. scope:'team' returns your POOLED TEAM network instead: the distinct total known by ANY teammate plus each member's own network size + consent tier. For overall 'how many…' questions; for 'how many <role/type>' use search_people with the role filter and read total.

Input Schema

NameRequiredDescriptionDefault
scopeNo'own' (default) — your network. 'team' — the pooled team network (total + per-member sizes).
team_idNoFor scope:'team' — one team's team_id (from account_status.teams). Omit it to summarize every team you're in: `total` counts a person two teams share once and `teams` has one summary per team.

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). Omit it to summarize every team you're in: `total` counts a person two teams share once and `teams` has one summary per team."
  2. Changed1 schema field changed
    • 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. 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": {
+        "scope": {
+          "enum": [
+            "own",
+            "team"
+          ],
+          "type": "string"
+        },
+        "sources": {
+          "items": {
+            "additionalProperties": true,
+            "properties": {},
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "team": {
+          "$ref": "#/properties/data/properties/sources/items"
+        },
+        "teams": {
+          "$ref": "#/properties/data/properties/sources"
+        },
+        "total": {
+          "type": "number"
+        }
+      },
+      "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.6/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world read. Beyond that the description discloses behavior the annotations cannot: no paging required, and that team scope returns a pooled distinct total (deduped across teammates) plus each member's own size and consent tier.

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?

Front-loads the core capability, then the team-scope exception, then the routing rule — a sensible order with no filler sentences. It is dense with em-dash clauses and repeats a little of what the schema already states, but every sentence carries information.

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 a two-parameter read tool with an output schema and full annotation coverage, nothing an agent needs is missing: purpose, scope semantics, aggregation caveats, and the alternative tool are all covered.

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 the schema already defines both params and the omit-team_id behavior; baseline would be 3. The description still adds meaning — 'distinct total known by ANY teammate' and the consent-tier notion — which clarifies what the pooled number actually represents, though some of this overlaps the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (network) and specific output content — total people, breakdowns by source/company, recent vs stale — plus a distinct team-scope mode. It also explicitly separates itself from search_people, so an agent can pick it without opening the schema.

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

Usage Guidelines5/5

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

Gives an explicit routing rule: use this for overall 'how many…' questions, and use search_people with a role filter for 'how many <role/type>'. It also names the condition that selects the team mode (scope:'team') and what that mode returns instead.

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