Skip to main content
Glama
OneMira MCP Server

OneMira MCP Server

Official

mira_wiki_list

Read-onlyIdempotent

Lists structured OKF Markdown wiki pages—topics, project notes, speaker profiles, and tasks—from a local OneMira vault without requiring a search query, so you can browse vault contents by folder.

Instructions

Enumerate structured OKF Markdown Wiki pages (topics, project notes, speaker profiles, and tasks.md) stored in the local OneMira vault without requiring a search query.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of Wiki page slugs to return (1–200, default 50).
folderNoVault scope to enumerate: "all", "wiki", "wiki/topics", or "wiki/people".all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is fully covered. The description adds useful scope detail (which page types live in the vault), but says nothing about ordering, return shape (slugs), or how limit interacts with total result count.

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?

A single tightly-written sentence with the resource and content scope front-loaded and zero filler. Nothing redundant and nothing repeated from the schema.

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, read-only two-parameter enumeration tool with rich annotations and a fully documented schema, the description covers purpose, scope, and content types adequately. The only gap is that the return representation (slugs) and result ordering are never stated.

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%, with both limit and folder fully documented including ranges, defaults, and the enum values. The description adds no parameter-level meaning beyond that, so baseline 3 applies.

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?

Uses a specific verb ("Enumerate") plus a well-defined resource (structured OKF Markdown Wiki pages) and enumerates the page categories covered (topics, project notes, speaker profiles, tasks.md), plus vault locality. It signals the contrast with search-based tools via "without requiring a search query," but never names the sibling (mira_search) that would handle the query case.

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 phrase "without requiring a search query" implies the usage condition: reach for this when you want a full listing rather than a targeted lookup. However, there are no explicit when-not rules, no mention of mira_wiki_read for fetching a page, and no prerequisites stated.

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