Skip to main content
Glama
bezata

kObsidian MCP

by bezata
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Analyze Note Tags

tags.analyze
Read-onlyIdempotent

Extract tags from a single note, separating frontmatter, inline, and de-duplicated union. Use to analyze one note's tags without scanning the entire vault.

Instructions

Return the tags present in a single note, split into frontmatterTags, inlineTags, and their de-duplicated union allTags. Use this when you have one note and want to know what tags it carries — contrast with tags.search, which scans the whole vault for one specific tag. Read-only.

Operates on the session-active vault (see vault.current — selectable via vault.select) unless an explicit vaultPath argument is passed, which always wins.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesVault-relative note path to analyze.
vaultPathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
allTagsYesUnion of frontmatter and inline tags, de-duplicated.
inlineTagsYes
frontmatterTagsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.5
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed8 schema fields changedv0.1.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / description
      Added value: +"Arguments for `tags.analyze`."
    • addedInput schema / properties / path / description
      Added value: +"Vault-relative note path to analyze."
    • addedOutput schema / properties / allTags
      Added value: +{
+  "description": "Union of frontmatter and inline tags, de-duplicated.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / frontmatterTags
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / inlineTags
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / path
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / required
      Added value: +[
+  "path",
+  "frontmatterTags",
+  "inlineTags",
+  "allTags"
+]
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces 'Read-only.' It adds context about the session-active vault and how `vaultPath` overrides it, which is valuable beyond the annotations. It does not detail the output format, but the presence of an output schema covers that.

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 that are front-loaded with the core purpose, then immediately disambiguate from the sibling. No filler or repetition—every sentence adds value.

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?

Given the output schema exists and the description clearly explains the tool's scope, usage context, and vault-selection nuances, an agent has enough to call it correctly. The only minor gap is the lack of detail on `vaultPath` formatting, but that's handled by the schema and the explicit 'always wins' note.

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 only 50% — `vaultPath` has no description in the schema. The description partially compensates by stating that `vaultPath` overrides the active vault, but it doesn't explain its format or default behavior in depth. This is adequate but not fully compensating for the low coverage.

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 states a specific verb (return), resource (tags in a single note), and the structure of the output (frontmatterTags, inlineTags, allTags). It explicitly contrasts with tags.search, making it unmistakably distinct from the closest sibling.

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 says 'Use this when you have one note and want to know what tags it carries' and names the alternative `tags.search` for whole-vault scans. Also explains the vault selection behavior and precedence of the `vaultPath` argument, leaving no ambiguity about when to call it.

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