AI Design Blueprint

Summarize Team Usage

team.summarize

Read-onlyIdempotent

Teams/Enterprise: summarises the caller's tool-usage patterns and value signals over a configurable window (default 30 days). Returns period_days, most_used_tools (call counts and average latency), value_events by event_type, observed_usage_stage, validator_lenses_used, recommended_next_assets and private_session. WHEN TO CALL: the user asks 'how is the Blueprint helping me/my team', 'what should I explore next', or 'show me my Blueprint usage'. WHEN NOT TO CALL: proactively or on every conversation turn (the summary is an explicit retrospective, not telemetry); to compare users (returns only the caller's own data). BEHAVIOR: read-only, idempotent over the same window. Aggregates from your tool-call log and value events. private_session has no effect here: this read stores no run, and the per-call tool-usage record is written on every call, as the privacy page states. Auth: Bearer , Teams or Enterprise plan; every other plan is refused. Data at rest in the UK.

Input Schema

Name	Required	Description	Default
`days_back`	No	Number of days of usage history to include in the summary.
`private_session`	No	No effect on this tool: accepted only so clients can pass the same flag to every tool. This read stores no run, and the per-call tool-usage record is written on every call.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 11, 2026

changedInput schema / properties / private_session / description

Previous value: -"Set to true to skip the per-call tool-usage record for this read."New value: +"No effect on this tool: accepted only so clients can pass the same flag to every tool. This read stores no run, and the per-call tool-usage record is written on every call."

Changed1 schema field changedOct 7, 2026

changedInput schema / properties / private_session / description

Previous value: -"Set to true to skip logging this summary call."New value: +"Set to true to skip the per-call tool-usage record for this read."

Changed1 schema field changedMay 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "summarize_team_usageDictOutput",
+  "type": "object"
+}

Changed1 schema field changedMay 9, 2026

changedOutput schema / (root)

Previous value: -{
-  "$defs": {
-    "ErrorBody": {
-      "description": "The body of `error_payload(code, message, details)` returns.",
-      "properties": {
-        "code": {
-          "title": "Code",
-          "type": "string"
-        },
-        "details": {
-          "additionalProperties": true,
-          "title": "Details",
-          "type": "object"
-        },
-        "message": {
-          "title": "Message",
-          "type": "string"
-        }
-      },
-      "title": "ErrorBody",
-      "type": "object"
-    }
-  },
-  "properties": {
-    "error": {
-      "$ref": "#/$defs/ErrorBody",
-      "default": null
-    },
-    "guidance": {
-      "default": null,
-      "title": "Guidance",
-      "type": "string"
-    },
-    "member_count": {
-      "default": null,
-      "title": "Member Count",
-      "type": "integer"
-    },
-    "members": {
-      "default": null,
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "title": "Members",
-      "type": "array"
-    },
-    "period": {
-      "additionalProperties": true,
-      "default": null,
-      "title": "Period",
-      "type": "object"
-    },
-    "plan": {
-      "default": null,
-      "title": "Plan",
-      "type": "string"
-    },
-    "summary": {
-      "additionalProperties": true,
-      "default": null,
-      "title": "Summary",
-      "type": "object"
-    },
-    "workspace_id": {
-      "default": null,
-      "title": "Workspace Id",
-      "type": "string"
-    }
-  },
-  "title": "TeamSummarizeResponse",
-  "type": "object"
-}New value: +null

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "ErrorBody": {
+      "description": "The body of `error_payload(code, message, details)` returns.",
+      "properties": {
+        "code": {
+          "title": "Code",
+          "type": "string"
+        },
+        "details": {
+          "additionalProperties": true,
+          "title": "Details",
+          "type": "object"
+        },
+        "message": {
+          "title": "Message",
+          "type": "string"
+        }
+      },
+      "title": "ErrorBody",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "error": {
+      "$ref": "#/$defs/ErrorBody",
+      "default": null
+    },
+    "guidance": {
+      "default": null,
+      "title": "Guidance",
+      "type": "string"
+    },
+    "member_count": {
+      "default": null,
+      "title": "Member Count",
+      "type": "integer"
+    },
+    "members": {
+      "default": null,
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "title": "Members",
+      "type": "array"
+    },
+    "period": {
+      "additionalProperties": true,
+      "default": null,
+      "title": "Period",
+      "type": "object"
+    },
+    "plan": {
+      "default": null,
+      "title": "Plan",
+      "type": "string"
+    },
+    "summary": {
+      "additionalProperties": true,
+      "default": null,
+      "title": "Summary",
+      "type": "object"
+    },
+    "workspace_id": {
+      "default": null,
+      "title": "Workspace Id",
+      "type": "string"
+    }
+  },
+  "title": "TeamSummarizeResponse",
+  "type": "object"
+}

First observedMay 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds material context beyond them: the aggregation sources (tool-call log plus value events), the auth and plan gate (Bearer token, Teams or Enterprise, all other plans refused), and UK data residency. It also resolves an easily-misread flag by explaining that private_session has no effect here because the underlying usage record is always written.

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-loaded with purpose, then clearly labelled WHEN TO CALL / WHEN NOT TO CALL / BEHAVIOR / Auth blocks that are easy to scan. It is long, and the private_session caveat duplicates the schema text, so one clause does not fully earn its place.

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?

Output schema exists, so return values need no explanation, yet the definition still covers plan gating, auth, data residency, aggregation sources, and the no-op flag. For a scoped retrospective read tool, nothing an agent needs in order 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and both parameters are documented in the schema, so the baseline is 3. The description adds only a mild restatement ('configurable window, default 30 days') and repeats the schema's private_session explanation almost verbatim, so it does not meaningfully exceed the schema.

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 verb+resource ('summarises the caller's tool-usage patterns and value signals') and scopes it to a configurable window with a stated default. It also enumerates the response shape, so an agent can distinguish this retrospective summary from sibling tools like me.sessions or signals.report without opening a 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?

Explicit WHEN TO CALL with three literal user phrasings ('how is the Blueprint helping me/my team', 'what should I explore next', 'show me my Blueprint usage') and an explicit WHEN NOT TO CALL covering both proactive invocation and misuse as a user-comparison tool. The routing guidance is about as unambiguous as it gets.

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

All AI Design Blueprint 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?