Skip to main content
Glama
Sign In
mingle-mcp

mingle-mcp

by aeoess
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_matches

Discover relevant people on the Mingle network by describing your needs and offers. Get ranked matches based on semantic similarity, even when browsing anonymously without a published card.

Instructions

Find people relevant to you on the Mingle network. Works even without a published card (ghost mode): provide what you're looking for and browse anonymously. Returns ranked matches based on semantic similarity between needs and offers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
min_scoreNoMinimum relevance score 0-1 (default: 0.3)
max_resultsNoMax results (default: 15)
query_needsNoGhost mode: describe what you need without a published card
query_offersNoGhost mode: describe what you offer without a published card

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / max_results / description
      Previous value: -"Max results (default: 10)"New value: +"Max results (default: 15)"
    • changedInput schema / properties / min_score / description
      Previous value: -"Minimum relevance score (default: 0)"New value: +"Minimum relevance score 0-1 (default: 0.3)"
    • addedInput schema / properties / query_needs
      Added value: +{
+  "description": "Ghost mode: describe what you need without a published card",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / query_offers
      Added value: +{
+  "description": "Ghost mode: describe what you offer without a published card",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Without annotations, the description carries full burden. It discloses ghost mode and anonymous browsing, but does not explicitly state read-only nature, authentication needs, or side effects. While helpful, it lacks comprehensive behavioral disclosure expected for a mutation-ambiguous tool.

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?

The description is three concise sentences, each serving a clear purpose: stating the main function, highlighting ghost mode capability, and explaining how results are ranked. No fluff or redundancy.

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?

With no output schema, the description should detail return values. It mentions 'ranked matches based on semantic similarity' but does not specify the structure of the matches, fields returned, or pagination. This leaves some ambiguity for an agent invoking the tool.

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?

All parameters are described in the schema (100% coverage), so baseline is 3. The description adds context like 'ghost mode' and 'browse anonymously', which mirrors the schema descriptions for query_needs and query_offers. It does not provide significant additional meaning beyond what the schema already offers.

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?

The description clearly states the tool's purpose: finding relevant people on the Mingle network. It specifies the verb 'find', the resource 'people', and key context like ghost mode and semantic similarity ranking. This distinguishes it from sibling tools which handle publishing, rating, and introductions.

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?

The description implies usage scenarios, such as when the user has no published card (ghost mode). However, it lacks explicit guidance on when not to use this tool or how it compares to alternatives like get_digest or other search functions. Usage context is implied but not fully articulated.

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

Deploy Server

Other Tools