Practitioner Knowledge MCP

Store idea

store_idea

Save a new idea to your private knowledge base by providing its title, domain, problem, and insight. Returns the stored record and its unique ID for later retrieval.

Instructions

Save a new idea to the knowledge base. Returns its id and the stored record.

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": {
      "title": "<title>",
      "domain": "<domain>",
      "problem": "<problem>",
      "insight": "<insight>"
    },
    "name": "store_idea"
  }
}

Input Schema

Name	Required	Description	Default
`tags`	No	Up to 20 short tags.
`title`	Yes	Short title, 3 to 200 characters.
`domain`	Yes	Subject area, such as 'public finance'.
`status`	No	Maturity of the idea.	seed
`insight`	Yes	The proposed answer or mechanism.
`problem`	Yes	The puzzle or question the idea addresses.
`assumptions`	No	Baseline assumptions the idea depends on.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 1, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the agent knows this is a non-destructive write operation. The description adds that it returns the id and stored record. However, it doesn't mention permission requirements, rate limits, or what happens on duplicate titles. With annotations covering safety, this is adequate but not rich.

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?

Two concise sentences that front-load the core action and then note the return value. No wasted words, though the second sentence is somewhat redundant given the output schema.

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?

The tool has 7 parameters, an output schema, and annotations, so the description doesn't need to explain return values in detail. However, it lacks usage guidance and behavioral nuances like validation rules or error handling. It is minimally complete but leaves gaps.

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%, so all parameters are fully documented in the schema. The description adds no extra parameter semantics beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description states a specific verb and resource: 'Save a new idea to the knowledge base.' An agent can distinguish this from siblings like get_idea or update_idea, though it doesn't explicitly contrast with them. The purpose is clear but lacks sibling differentiation.

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?

The description offers no guidance on when to use this tool versus alternatives such as update_idea (for existing ideas) or search_ideas. There is no mention of prerequisites or context. This is a significant gap for a creation tool with multiple related siblings.

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

Deploy Server