Skip to main content
Glama

obsidian_get_moc

Extracts interconnected notes from one of the seven Hubs or MOCs in the Obsidian vault, helping you retrieve a map of content and its linked notes by specifying the MOC name.

Instructions

Extrait les notes interconnectées depuis l'un des 7 Hubs/MOCs du coffre

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": {
      "moc": "<moc>"
    },
    "name": "obsidian_get_moc"
  }
}

Input Schema

NameRequiredDescriptionDefault
mocYesNom du MOC central à consulter (ex: 'Index-Projets', 'Index-Stack')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a read of linked notes but says nothing about traversal depth (direct links only vs recursive), whether full content or just titles/links are returned, error behavior for an invalid hub, or any permission requirements.

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?

One short, front-loaded sentence with no filler or redundancy. It is efficient, though its brevity contributes directly to the missing behavioral detail noted elsewhere.

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 simple (one enum parameter, no output schema), so little explanation is needed. Still, an agent cannot tell what the response looks like — a list of note names, links, or full note bodies — which matters for deciding whether to use this tool or a note reader.

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% and the single parameter's enum fully enumerates the 7 allowed hubs. The description only restates the constraint ('l'un des 7 Hubs/MOCs') and adds no syntax, case-sensitivity, or fallback guidance beyond the schema.

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?

States a specific verb and resource ('Extrait les notes interconnectées') scoped to a named domain ('l'un des 7 Hubs/MOCs du coffre'). An agent can distinguish this from a generic note read, though the description never names the siblings it differs from.

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

Usage Guidelines3/5

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

Usage is only implied: fetch notes from a hub/MOC rather than a single note. There is no explicit when-to-use, when-not-to-use, or comparison against obsidian_read_note or obsidian_search_notes, which are the obvious alternatives for retrieving notes.

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