hunchful

Relay: find people to talk to

find_people

Read-only

Find people to talk to — for someone who'd like new company, a collaborator, or a friend. Searches people who listed themselves, by collaboration style from the person's Hunchful model (mode 'complement' = works differently in ways that help, 'similar' = alike), shared interests, and place. Returns ALIASES and only what each person chose to show, plus an inspectable 'why' — never names or identities. To make contact, use knock with a result's ref, and only with the person's approval.

Input Schema

TableJSON 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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`hint`	No
`note`	Yes
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

A4/5.0

Behavior4/5

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

Annotations already establish read-only/non-destructive, and the description adds genuinely new behavioral context: results are alias-only with 'never names or identities', each result carries an inspectable 'why', and contact requires the person's approval via knock. That consent model and privacy guarantee are not derivable from annotations or the input schema.

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?

Purpose is front-loaded in the first clause, and the paragraph is dense but nearly every clause adds information (matching dimensions, return privacy, contact path). The em-dashed parentheticals and single run-on structure make it slightly heavier than needed.

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?

An output schema exists, so return-shape explanation is optional, yet the description still clarifies the alias-only/'why' nature of results, which matters for agent interpretation. The one real gap for an 8-parameter tool is sibling disambiguation among the many find_* / search_* peers.

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 moderate (63%), and the description compensates where it matters most: it defines mode semantics ('complement' = works differently in ways that help, 'similar' = alike) that the schema leaves as ambiguous as 'Default complement'. It also covers the interests/place matching dimensions, though openTo, languages and limit are left to the schema.

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?

States a specific verb+resource (find people) and narrows it sharply: 'people who listed themselves', matched by collaboration style, interests and place. It does not, however, name or distinguish itself from the many adjacent search siblings (find_matches, find_complementary_thinkers, search_profiles), so an agent must infer which search tool applies.

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

Usage Guidelines4/5

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

Gives clear use-case framing (new company, collaborator, friend) and an explicit next-step route: 'To make contact, use knock with a result's ref, and only with the person's approval.' No explicit when-not-to-use or sibling exclusion is stated, so the agent isn't told when find_matches would be the better call.

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

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.