okf-mcp

okf_suggest_concept_path

Read-onlyIdempotent

Suggest a safe bundle-relative Markdown path from a concept type and title, including an optional directory prefix.

Instructions

Suggest a safe bundle relative Markdown path from a concept type and title.

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": {
      "type": "<type>",
      "title": "<title>"
    },
    "name": "okf_suggest_concept_path"
  }
}

Input Schema

Name	Required	Description
`type`	Yes	Concept type used to build the path.
`title`	Yes	Concept title used to build the file name.
`bundle`	No	Writable root id; optional when exactly one local root is configured.
`prefix`	No	Optional bundle relative directory prefix.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.9.0Aug 25, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations (readOnlyHint=true, destructiveHint=false, idempotentHint=true) already establish the safe, non-destructive nature. The description adds the word 'safe', which is not explained further, but it does not contradict annotations. Minimal additional behavioral context is provided beyond what annotations already convey.

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 a single, efficient sentence that directly states the tool's function. No filler, no redundancy, and the core action is front-loaded. It is an excellent example of concise specification.

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?

For a simple utility tool with four well-documented parameters and no output schema, the description adequately conveys what it does. It implies that the tool returns a path (since it 'suggests' one), and the 'safe' qualifier hints at validation. Given the low complexity, it is 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?

Schema description coverage is 100%, so every parameter already has a clear description. The tool description does not add any additional meaning to the parameters, such as constraints, format expectations, or relationships. The schema does the heavy lifting; the description simply restates the purpose without enriching parameter semantics.

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 ('Suggest') and resource ('bundle relative Markdown path'), and specifies the inputs ('from a concept type and title'). This clearly distinguishes it from siblings like find_paths (which deals with graph paths) and list_bundles (which deals with bundle listing). No ambiguity about what the tool produces.

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?

There is no guidance on when to use this tool versus alternatives, nor any conditions or prerequisites. It simply states what it does without contextualizing its use within the broader workflow. An agent would have to infer that this is a path construction helper, not something to be used for searching or listing.

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