Skip to main content
Glama
Sign In
Obsidian Dictionary MCP Server

Obsidian Dictionary MCP Server

by SaraHan774
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

search_entry

Check if a term exists in a glossary Markdown file. Returns true or false with the entry content if found.

Instructions

Check if a term already exists in the glossary. Returns true/false and the entry content if found.

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": {
      "term": "<term>"
    },
    "name": "search_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathNoPath to the glossary markdown file
termYesThe term to search for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided, and description lacks specificity on behavior when term not found, case sensitivity, or error handling. Does not disclose exact return format or side effects.

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?

Single sentence, clear and efficient. Could be slightly more structured but not overly verbose.

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

Completeness2/5

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

Given no output schema and only one required param, description does not address behavior when optional file_path is omitted. Lacks completeness about return details.

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 covers 100% of parameters with descriptions. Description adds no additional semantic value beyond schema.

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?

Clearly states it checks term existence in glossary and returns true/false with content. Distinguishes from siblings like append_entry, get_entry, list_terms.

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?

Implicitly tells when to use (check existence before adding), but no explicit alternatives or when not to use. Could provide more context about selection among siblings.

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