Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Metis · Librarian — Get Library Stats

get_library_stats

Summarize your literature library's total papers, source and item type breakdown, recent additions, and Zotero sync status before searching or citing.

Instructions

Summarise your literature library at a glance.

Use this to see how big and how current your reference collection is before
searching or citing: it reports the total number of papers, a breakdown by
source (e.g. Zotero, Mendeley, manual) and by item type, the most recently
added references, and — if you sync Zotero — when the library was last
synced. A quick "what's in my library right now?" overview. Takes no
arguments. Pairs with search_library and sync_zotero_library.

Returns:
    A formatted summary: total papers, counts by source and item type, the
    five most recent references, and Zotero sync state if available.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

The description discloses the read-only nature of the tool (no side effects implied) and details the returned information. With no annotations, the description carries the full burden, and it adequately describes what the tool does and returns.

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?

The description is well-structured with a clear introduction, usage context, and return summary. While somewhat lengthy, every sentence adds value and it is front-loaded with the purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters, no annotations, and presence of an output schema, the description fully explains what the tool returns and when to use it. It is complete for a simple stat retrieval tool.

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?

No parameters exist, so the schema provides no info. The description implicitly states it takes no arguments, which adds value beyond the empty schema.

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 clearly states it summarises the literature library, reporting total papers, breakdown by source and type, recent references, and sync status. It uses a specific verb ('summarise') and distinguishes itself from siblings like search_library and sync_zotero_library.

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?

Explicitly advises when to use: 'before searching or citing' to know library size and currency. It also notes it pairs with search_library and sync_zotero_library, providing clear context for selection.

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