Skip to main content
Glama
Sign In
okf-mcp

okf-mcp

by teomarcdhio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_concept

Creates a new OKF concept document with markdown body, tags, and frontmatter. Fails on duplicate IDs; use update_concept to modify.

Instructions

Create a new OKF concept document.

Fails if the concept already exists — use update_concept to modify existing ones.

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": {
      "concept_id": "<concept_id>",
      "type": "<type>"
    },
    "name": "create_concept"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoMarkdown body content.
tagsNoShort tag strings for cross-cutting categorisation.
typeYesConcept type (required by OKF spec). Examples: "Memory", "Note", "Insight", "Table", "Metric", "Playbook", "API", "Reference", "Dataset".
titleNoHuman-readable display name.
resourceNoOptional URI for the underlying asset or source.
concept_idYesPath relative to bundle root, without .md extension. Use subdirectories to organise knowledge: "memory/session_2024_01", "tables/orders", "metrics/wau"
descriptionNoOne-sentence summary (used in index files and search).
extra_frontmatterNoAdditional frontmatter key-value pairs.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/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 a critical behavioral trait: the tool fails if the concept already exists, preventing accidental overwrites. It also provides a fallback (update_concept). While it doesn't cover every possible side effect, the most important failure mode is clearly stated, which is above baseline for a create operation.

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?

Two sentences, front-loaded with the action, and every clause earns its place. The failure condition and alternative are conveyed with zero waste.

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?

The description is highly complete for an 8-parameter tool with 100% schema coverage, output schema present, and sibling context. It covers the core purpose, usage distinction, and failure mode. Minor gaps like OKF-specific conventions are addressed by the schema, so the description is sufficient to guide 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?

Schema description coverage is 100%, so baseline is 3. The description adds no information about parameters beyond the schema's existing thorough explanations (e.g., concept_id path, type examples). It doesn't compensate with extra semantics but doesn't need to given the schema quality.

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+resource ('Create a new OKF concept document') and clearly distinguishes itself from the sibling update_concept by stating 'use update_concept to modify existing ones.' This leaves no ambiguity about what the tool does and how it differs from related tools.

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

Usage Guidelines5/5

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

Explicitly states when to use this tool (for new concepts) and when to use the alternative ('Fails if the concept already exists — use update_concept to modify existing ones'). This covers both when and when-not, satisfying the highest bar for usage guidance.

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