MKP MCP Server

mkp_trigger_conversation

Analyze user conversations by providing input to the MKP system. Optionally include user profile data to enhance contextual reasoning through meta-knowledge processing.

Instructions

Trigger MKP system for conversation analysis

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": {
      "user_input": "<user_input>"
    },
    "name": "mkp_trigger_conversation"
  }
}

Input Schema

Name	Required	Description	Default
`user_input`	Yes	User input to trigger MKP conversation analysis
`user_profile`	No	Optional user profile data as JSON string	{}

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 25, 2026

TDQS

C2.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'trigger', implying initiation, but does not disclose side effects, authorization needs, or whether it is destructive or read-only. This is insufficient for an agent to understand the tool's behavior.

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?

The description is extremely short (one phrase) and lacks full sentences or structure. While it is concise, it sacrifices informativeness. It could be slightly more structured to improve readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 2 parameters, no output schema, and no annotations, the description is incomplete. It does not explain return values, error states, or relationships with siblings. For a tool that triggers a system, more context is needed for proper use.

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 description coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond the schema: it does not explain how parameters relate to the tool's purpose or provide format/syntax details. The schema already describes both parameters adequately.

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 description states 'Trigger MKP system for conversation analysis', which gives a general verb+resource but is vague and does not clearly distinguish from siblings like 'mkp_analyze_context' or 'mkp_enhance_cognition'. The purpose is implied but lacks specificity.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives. No exclusions or context provided. The description merely states the action without any situational context.

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

Deploy Server