Skip to main content
Glama
wuruiqi

academic-workflow-mcp

by wuruiqi

workflow_get_note

Fetch a literature note's content, path, and status from Obsidian vault using its citekey. Helps review written notes and decide whether to overwrite or patch.

Instructions

Read the current content of a literature note from the Obsidian vault.

Useful for reviewing what has already been written, checking the status, or deciding whether to overwrite vs. patch a note.

Args: citekey: Better BibTeX citekey (= filename without .md).

Returns: {"exists": bool, "path": str, "content": str, "status": str | None}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
citekeyYes
Behavior3/5

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

Discloses read-only nature and return schema but lacks details on auth, rate limits, or error handling. Since no annotations exist, additional behavioral context would be beneficial.

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?

Concise, front-loaded, every sentence adds value. Args and returns clearly formatted with no extraneous text.

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?

Covers purpose, usage, parameter, and return format adequately for a simple read tool. Minor missing details like behavior on missing notes are implied by the return structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description fully explains the sole parameter 'citekey' as a Better BibTeX citekey equivalent to filename without .md, which is critical given 0% schema description coverage.

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?

Clearly describes reading a literature note from Obsidian vault with specific verb and resource. Could explicitly differentiate from siblings like workflow_write_note, but the context is sufficient.

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?

Provides use cases (review, check status, decide overwrite/patch) but does not explicitly state when not to use or name alternatives among siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wuruiqi/academic-workflow-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server