Skip to main content
Glama
Sign In
ragnarok

ragnarok

by freyr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

open_projects

List active projects from Obsidian vaults grouped by SUMMARY.md state, sorted by update date descending, with optional vault and state filters.

Instructions

The projects that are open, grouped by the state in their SUMMARY.md, newest update first.

states defaults to in-progress and paused; the other values are done, superseded and abandoned. Each project has its slug, vault, folder, description, stage, state, gate, updated date and next action.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "open_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
vaultNo
statesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden and does add real behaviour: default state filter, allowed state values, grouping semantics and sort order. It omits permissions, result limits/pagination, and whether an explicit empty states list means 'all' or 'none'.

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?

Front-loaded with the core purpose in the first clause, followed by ordering and state semantics. The trailing enumeration of returned fields is largely wasted given an output schema exists, but the description stays short.

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?

An output schema exists, so per-record fields need not be described; the description redundantly lists them but isn't missing anything critical except the `vault` parameter semantics. For a simple two-parameter list tool this is close to 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 0%, so the description must compensate. It documents `states` well (default of in-progress and paused; the other valid values are done, superseded and abandoned), but `vault` is never mentioned, leaving one of two parameters with no meaning beyond its bare name.

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?

States a specific verb+resource ('The projects that are open'), plus grouping key (state in SUMMARY.md) and ordering (newest update first). It is clear what the tool returns, but it never distinguishes itself from siblings like find_projects or list_project, which sound like overlapping project-listing tools.

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?

Usage is only implied: the description explains the default filter (in-progress and paused) and the alternate state values, which tells the agent how to broaden or narrow results. It gives no explicit when-to-use versus find_projects/search or when-not guidance.

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