Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Metis · Librarian — Index Pending Layers

index_pending_layers

Indexes pending knowledge layers with manually added documents, skipping layers already indexing. Set confirm to false to report pending work without starting.

Instructions

Index every knowledge layer that has documents waiting (Keystone M6).

The sweep behind "I dropped a PDF into the folder". Pack installs and Zotero
imports schedule their own indexing, but a file copied in by hand — which is
what _TO-OBTAIN.md asks for — has no code path to notice it. This closes that
gap, and is what the nightly job should call.

Runs detached and single-flight: a layer already indexing is left alone rather
than started twice.

Args:
    confirm: False to report what is pending without starting anything.

Input Schema

NameRequiredDescriptionDefault
confirmNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

A4.5/5.0
Behavior4/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, and it does well: it discloses detached/background execution (no inline result), single-flight semantics (an already-indexing layer is skipped rather than double-started), and a dry-run mode. It omits failure behaviour and required permissions, which keeps it short of a 5.

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 action, then rationale, then behaviour, then the argument. Minor waste remains in the internal markers '(Keystone M6)' and the reference to a private file convention, which add no decision-relevant information for an agent.

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 one-parameter background sweep with an output schema, the agent has what it needs: scope, exclusion, idempotency and dry-run. Only error/handling detail is absent, which is a small gap given the tool returns via an output schema.

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

Parameters4/5

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

Schema coverage is 0%, so the description carries the burden, and it defines confirm as a dry-run switch: false reports what is pending without starting anything, implying true actually indexes. That fully disambiguates the single boolean, though it could state the default-True behaviour explicitly.

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?

States a specific verb and resource ('Index every knowledge layer that has documents waiting') and scopes it to the hand-copied-file case, explicitly excluding the cases already handled by pack installs and Zotero imports. An agent can tell it apart from index_library_pdfs, index_pdf_library or sync_zotero_local without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the triggering situation ('I dropped a PDF into the folder'), the caller that should use it (the nightly job), and the conditions under which it is not needed (pack installs and Zotero imports schedule their own indexing). That is an explicit when and when-not with alternatives identified.

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