Skip to main content
Glama
Sign In
okf-mcp

okf-mcp

by teomarcdhio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_index

Retrieve a directory's index.md from an OKF knowledge bundle to see its listed concepts. Returns empty if no index exists.

Instructions

Get the index.md content for a directory in the bundle.

Index files list the directory's concepts for progressive disclosure. Returns empty string if no index exists.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoDirectory path relative to bundle root. Leave empty for the root index.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses an important edge case: 'Returns empty string if no index exists.' It also clarifies the input scope ('directory in the bundle'). While it doesn't mention permissions or error handling, these are less critical for a straightforward read 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?

The description is two sentences: first states the action, second explains purpose and return behavior. It is front-loaded, concise, and every sentence adds value.

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

Completeness5/5

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

The tool is simple (one optional parameter, output schema exists). The description covers the main behavior, the empty-string edge case, and the purpose of index files, making it complete for an agent to correctly invoke the tool.

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 schema description coverage is 100%, fully describing the path parameter. The tool description adds no additional parameter semantics, so the baseline of 3 applies.

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 clearly states the tool's function: 'Get the index.md content for a directory in the bundle.' It uses a specific verb (Get) and resource (index.md content) and distinguishes itself from siblings like get_concept or get_log by focusing on directory-level index files.

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 gives clear context by explaining that index files list directory concepts for progressive disclosure, implying when this tool is appropriate. However, it does not explicitly name alternatives or provide when-not-to-use guidance, so it falls short of a 5.

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