Skip to main content
Glama
Sign In
Another bloated Obsidian MCP Server

Another bloated Obsidian MCP Server

by diegorv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_base

Retrieves the complete content of an Obsidian Base, including its schema and all rows, to provide full data access.

Instructions

Get the full content of an Obsidian Base including schema and all rows

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": {
      "path": "<path>"
    },
    "name": "get_base"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the .base file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are present, so the description must carry the behavioral disclosure burden. It clarifies that the tool performs a read operation and returns schema and rows, but it does not mention potential performance implications, permission requirements, or return format details, leaving gaps.

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 a single, front-loaded sentence that directly states the tool's function with no superfluous words. Every word earns its place.

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 simple one-parameter schema and clear purpose, the description is largely complete. It covers what the tool does (full content, schema, rows), though it could mention that query_base exists for filtered queries, which would make it fully comprehensive.

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?

The input schema has 100% coverage with 'path' described as 'Path to the .base file', which is clear. The description adds no further parameter semantics beyond the schema, so 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 states 'Get the full content of an Obsidian Base including schema and all rows', with a specific verb (Get), clear resource (Obsidian Base), and explicit scope (schema and all rows). This clearly distinguishes it from siblings like list_bases (listing) and query_base (querying).

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 use when full base content is needed, but it does not explicitly state when to use this tool instead of alternatives like query_base or list_bases. No exclusions or alternative recommendations are provided, so guidance is only implicit.

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