Skip to main content
Glama
Sign In
Obsidian MCP Learning System

Obsidian MCP Learning System

by dhruvvenkat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_learning_gaps

Identify likely weak spots in an Obsidian vault by scanning a folder for repeated but shallow concept coverage, helping you target study gaps and plan deeper review.

Instructions

Identify likely weak spots based on repeated but shallow concept coverage.

Args: vault_path: Absolute path to the Obsidian vault. folder: Folder inside the vault to scan.

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_learning_gaps"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderNo
vault_pathNo/home/dhruv/Documents/compiler engineering

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 behavioral burden. 'Scan' and 'identify' imply a read-only analysis, but the description does not explicitly state that the vault is not modified, whether an index is built, or how expensive the scan may be.

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?

The description is short and front-loaded: the purpose comes first, followed by a compact Args block. There is little wasted text, though the Args formatting is more Python docstring than agent-facing guidance.

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 is low-complexity with two parameters and an output schema, so return values need not be explained. Still, the description omits prerequisites such as whether concepts must first be extracted, and it does not clarify read-only behavior despite having no annotations.

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 0%, so the description must compensate. It does add meaning for both parameters: vault_path is an absolute path, and folder is a folder inside the vault. However, it does not mention that both are optional with defaults, nor does it explain the null behavior for folder.

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 analytical action: identify likely weak spots. It also explains the underlying signal, repeated but shallow concept coverage, so an agent knows this is not just listing notes. It does not name or distinguish itself from siblings like extract_concepts, but the purpose is clear.

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 explicit guidance on when to use this tool versus extract_concepts, generate_study_session, or compare_notes_to_project. The only implied usage is that it scans a vault or folder, with no prerequisites, exclusions, or alternative routes described.

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