hunchful

Relay: find people to talk to

find_people

Read-only

"Hitta någon som spelar padel": people who listed themselves, by what they do (text, interests), place and how they work. Returns aliases and what each chose to show, never who they are. To make contact: knock, with the person's yes. For a group to join: find_community_ideas.

Input Schema

Name	Required	Description
`city`	No
`mode`	No	Default 'complement'.
`text`	No	Free-text match in intros, interests, merits and views people chose to show.
`limit`	No	1–20, default 8.
`openTo`	No	What they're open to.
`region`	No
`interests`	No	Match anyone sharing at least one.
`languages`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 5, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / (root)

Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "hint": {
-      "type": "string"
-    },
-    "note": {
-      "type": "string"
-    },
-    "results": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "alias": {
-            "type": "string"
-          },
-          "city": {
-            "type": "string"
-          },
-          "interests": {
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          "intro": {
-            "type": "string"
-          },
-          "languages": {
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          "merits": {
-            "type": "string"
-          },
-          "openTo": {
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          "ref": {
-            "type": "string"
-          },
-          "region": {
-            "type": "string"
-          },
-          "style": {
-            "items": {
-              "additionalProperties": false,
-              "properties": {
-                "axis": {
-                  "type": "string"
-                },
-                "leans": {
-                  "type": "string"
-                }
-              },
-              "required": [
-                "axis",
-                "leans"
-              ],
-              "type": "object"
-            },
-            "type": "array"
-          },
-          "views": {
-            "type": "string"
-          },
-          "why": {
-            "additionalProperties": false,
-            "properties": {
-              "complementary": {
-                "items": {
-                  "additionalProperties": false,
-                  "properties": {
-                    "axis": {
-                      "type": "string"
-                    },
-                    "them": {
-                      "type": "string"
-                    },
-                    "why": {
-                      "type": "string"
-                    },
-                    "you": {
-                      "type": "string"
-                    }
-                  },
-                  "required": [
-                    "axis",
-                    "you",
-                    "them",
-                    "why"
-                  ],
-                  "type": "object"
-                },
-                "type": "array"
-              },
-              "sharedInterests": {
-                "items": {
-                  "type": "string"
-                },
-                "type": "array"
-              },
-              "similar": {
-                "items": {
-                  "$ref": "#/properties/results/items/properties/style/items"
-                },
-                "type": "array"
-              }
-            },
-            "required": [
-              "complementary",
-              "similar",
-              "sharedInterests"
-            ],
-            "type": "object"
-          }
-        },
-        "required": [
-          "ref",
-          "alias",
-          "intro",
-          "why"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "results",
-    "note"
-  ],
-  "type": "object"
-}New value: +null

Changed7 schema fields changedSep 25, 2026

addedInput schema / properties / languages

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / openTo

Added value: +{
+  "description": "What they're open to.",
+  "items": {
+    "enum": [
+      "coffee",
+      "walks",
+      "online chat",
+      "collaboration",
+      "mentoring",
+      "study buddy",
+      "hobby partner",
+      "language exchange"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / text / description

Previous value: -"Free-text match in intros."New value: +"Free-text match in intros, interests, merits and views people chose to show."

addedOutput schema / properties / results / items / properties / languages

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / results / items / properties / merits
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / results / items / properties / openTo

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / results / items / properties / views
```
Added value: +{
+  "type": "string"
+}
```

AddedSep 25, 2026

TDQS

B3.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered; the description adds genuinely non-obvious behavior: results are aliases and only what each person chose to disclose, never their real identity, and contact requires a knock accepted by the person.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads a usage example, but the Swedish quoted phrase and compressed clauses ('place and how they work') cost clarity rather than saving space; the sentences are terse yet under-specified.

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?

For an 8-parameter discovery tool with no output schema, the privacy and consent semantics are well covered, but the matching semantics (what complement vs similar vs any actually do), pagination/limits and language filtering are left for the agent to infer.

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 63%, so the baseline is roughly 3. The description echoes text, interests and place but leaves mode (complement/similar/any), openTo, languages and the 1-20 limit unexplained, and the phrase 'how they work' ambiguously gestures at a parameter without clarifying which one or what its values mean.

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

Purpose3/5

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

The verb and resource are present ('find people who listed themselves') along with the filter axes (text, interests, place), but the phrasing is oblique: 'by what they do' and 'how they work' are not concrete field references, and the tool is never distinguished from the overlapping sibling search_profiles or the generic search.

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?

It routes follow-on intent usefully — say to use knock (with the person's consent) to make contact and find_community_ideas to join a group — but it gives no guidance on when this search is preferable to search_profiles, list_members, or plain search, and it states no exclusions or prerequisites.

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

All hunchful 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.

Relay: find people to talk to

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources