Skip to main content
Glama
Sign In
Obsidian Dictionary MCP Server

Obsidian Dictionary MCP Server

by SaraHan774
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_entry

Retrieve a specific glossary entry by term name, returning only that definition without loading the entire file.

Instructions

Retrieve a specific entry from the glossary by term name. Returns only that entry, not the whole file.

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": "get_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathNoPath to the glossary markdown file
termYesThe term to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/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 burden. It states that the tool returns only the entry (not the whole file), which hints at read-only behavior, but it does not disclose potential errors (e.g., term not found), permission requirements, or side effects. This is insufficient for a tool with no annotation support.

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, front-loading the purpose. Every word adds value with no redundancy or filler. It is appropriately sized for the tool's simplicity.

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?

For a simple retrieval tool with 2 parameters and no output schema, the description covers the core purpose and return scope. It could improve by mentioning error handling or the role of the optional file_path, but overall it is mostly complete.

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 100%, so the input schema already documents both parameters. The description adds context about the return behavior but does not enhance parameter meaning beyond what the schema provides. Baseline 3 is appropriate.

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 action ('Retrieve'), the resource ('specific entry from the glossary'), and the method ('by term name'). It distinguishes from siblings by emphasizing it returns only one entry, not the whole file, differentiating it from list_terms and search_entry.

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?

The description implies usage when you need a specific entry by term name, but it does not provide explicit guidance on when to use this tool versus its siblings (append_entry, list_terms, search_entry). No when-not or alternative conditions are stated.

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