Skip to main content
Glama
Sign In
mingle-mcp

mingle-mcp

by aeoess
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

remove_intent_card

Remove an intent card from the Mingle network while preserving identity and connection history. Enables publishing a fresh card later.

Instructions

Remove your card from the Mingle network. Your identity and connection history are preserved. Publish a fresh card anytime.

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": {
      "card_id": "<card_id>"
    },
    "name": "remove_intent_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
card_idYesCard ID to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description adds behavioral context: it states removal preserves identity and history, and is reversible via republishing. It does not mention potential side effects or permissions, but adequately highlights non-destructive nature.

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 two sentences, front-loading the core purpose in the first sentence. Every sentence adds value (purpose + reassurance). No verbose or redundant content.

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 simplicity (single parameter, no output schema), the description covers purpose, main effect, and key behavioral traits. It omits details like error handling or prerequisites, but is generally sufficient for correct invocation.

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?

The input schema covers 100% of parameters with a description for 'card_id'. The description adds no additional parameter semantics beyond what the schema 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 uses a specific verb ('Remove') and resource ('your card'), clearly stating the action. It distinguishes itself from the sibling 'publish_intent_card' by mentioning 'Publish a fresh card anytime', indicating a contrasting 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?

The description implies when to use (when you want to remove your card) and provides context that identity and connection history are preserved, and republishing is possible. However, it lacks explicit exclusions or comparisons to other tools beyond the publishing hint.

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