Skip to main content
Glama

Overlap

by com.overlap-ai
OverviewDiscussionsAdmin

See how many people are going through something similar

preview_pool
Read-onlyIdempotent

Count people in overlap's peer-connection pool who are going through a similar personal situation. Use when the user asks whether another person shares their situation before deciding whether to join. Do not use for intersections of lists, sets or schedules, dating, or finding licensed professionals. Returns a number and nothing else, capped at 10 — never anyone's words, name or details. It saves nothing: no match request is created and nobody is contacted. This is the one tool that works without an account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionYesWhat the person is going through, in their own words. Two to five sentences is enough. This is only embedded and counted against — it is never stored and never shown to anyone.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesPeople in the pool with a similar situation, at most 10.
cappedYesTrue when the count hit the cap of 10.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "capped": {
+      "description": "True when the count hit the cap of 10.",
+      "type": "boolean"
+    },
+    "count": {
+      "description": "People in the pool with a similar situation, at most 10.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "count",
+    "capped"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds substantial unannotated behavior: output is only a number capped at 10, no names or details are ever returned, nothing is persisted, no contact occurs, and it is the one tool usable without an account.

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?

Five short sentences, each carrying distinct information (trigger, exclusions, return shape, side-effect profile, auth requirement), with the core purpose front-loaded. No filler or repetition.

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?

An output schema exists, yet the description still usefully summarizes the return as a capped number, and it fully covers privacy, persistence, contact, and auth behavior. An agent has everything needed to decide and invoke correctly.

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% and the parameter's own description already explains the free-text format and that it is embedded and never stored. The tool description adds no parameter-level syntax or constraints beyond that, so the baseline 3 applies.

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 (count) and resource (people in overlap's peer-connection pool matching a described situation), and is clearly separable from the match-request lifecycle siblings (create_match_request, respond_to_match, etc.). The title and description together make the intent unmistakable.

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 trigger ('when the user asks whether another person shares their situation before deciding whether to join') plus concrete exclusions (list/set/schedule intersections, dating, licensed professionals). It also implicitly routes the follow-up action to the join/match-request flow.

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

All Overlap toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold 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