mingle-mcp

publish_intent_card

Publish your intent card to the Mingle network—specify your needs and offers—and receive top matches instantly.

Instructions

Publish your profile to the Mingle network — what you're looking for and what you can offer. Cards are Ed25519 signed with your persistent identity and expire after 48h. Returns your top matches immediately.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description
`name`	Yes	Your name or alias
`topic`	No	What you're working on (short summary)
`needs`	No	What you're looking for (plain text list)
`offers`	No	What you can provide (plain text list)
`context`	No	Rich context for better matching (private — never shown to others)
`open_to`	No	Open to (e.g. 'introductions', 'partnerships')
`hours`	No	Hours until card expires (default 48)

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedMay 7, 2026

addedInput schema / properties / context

Added value: +{
+  "description": "Rich context for better matching (private — never shown to others)",
+  "type": "string"
+}

changedInput schema / properties / hours / default
```
Previous value: -24New value: +48
```

changedInput schema / properties / hours / description

Previous value: -"Hours until card expires"New value: +"Hours until card expires (default 48)"

changedInput schema / properties / needs / description

Previous value: -"What you're looking for"New value: +"What you're looking for (plain text list)"

removedInput schema / properties / needs / items / additionalProperties
```
Removed value: -false
```

removedInput schema / properties / needs / items / properties

Removed value: -{
-  "category": {
-    "description": "Category (e.g. 'engineering', 'design', 'funding', 'marketing')",
-    "type": "string"
-  },
-  "description": {
-    "description": "What is needed or offered",
-    "type": "string"
-  },
-  "priority": {
-    "default": "medium",
-    "enum": [
-      "critical",
-      "high",
-      "medium",
-      "low"
-    ],
-    "type": "string"
-  },
-  "tags": {
-    "description": "Tags for matching",
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  }
-}

removedInput schema / properties / needs / items / required
```
Removed value: -[
-  "category",
-  "description"
-]
```
changedInput schema / properties / needs / items / type
```
Previous value: -"object"New value: +"string"
```

removedInput schema / properties / not_open_to

Removed value: -{
-  "description": "Not open to (e.g. 'cold-sales', 'recruitment-spam')",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

changedInput schema / properties / offers / description

Previous value: -"What you can provide"New value: +"What you can provide (plain text list)"

removedInput schema / properties / offers / items / $ref
```
Removed value: -"#/properties/needs/items"
```
addedInput schema / properties / offers / items / type
```
Added value: +"string"
```

addedInput schema / properties / topic

Added value: +{
+  "description": "What you're working on (short summary)",
+  "type": "string"
+}

First observedv1.0.0Mar 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It discloses key traits: Ed25519 signing, 48h expiry, and immediate match returns. However, it does not explain mutation semantics (e.g., whether publishing overwrites an existing card) or authentication requirements.

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 sentences, front-loading the main purpose and then adding behavioral details. Every sentence provides value with no redundancy.

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?

Given the tool's complexity (7 params, no output schema, no annotations), the description covers the main behavioral aspects (signing, expiry, immediate matches) and overall purpose. However, it omits details about idempotency, limits, or relationship with sibling tools like remove_intent_card.

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% with descriptions for all 7 parameters. The description does not add significant extra meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 publishes a profile card to the Mingle network. It specifies the verb 'publish' and the resource 'profile card', and distinguishes itself from siblings like search_matches and remove_intent_card by being the creation action.

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?

While the description implies use when wanting to publish an intent card, it does not explicitly contrast with sibling tools or provide when-not guidance. However, the overall purpose is clear enough to guide correct usage.

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

Deploy Server