Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Metis · Librarian — Configure Library Provider

configure_library_provider

Set up or switch the reference manager for this Metis installation by choosing Zotero or Mendeley and supplying the required API key, user ID, or BibTeX export path.

Instructions

Configure the library provider for this Metis installation.

Call this during setup or when switching reference managers.

Args:
    provider: "zotero" or "mendeley". Mendeley uses BibTeX export.
    api_key: Zotero API key (from https://www.zotero.org/settings/keys).
    user_id: Zotero numeric user ID (shown on the same settings page).
    bibtex_path: For Mendeley: full path to exported .bib file.

Input Schema

NameRequiredDescriptionDefault
api_keyNo
user_idNo
providerYes
bibtex_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/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. It explains provider-specific parameters and that Mendeley uses BibTeX export. However, it does not disclose whether the operation overwrites existing config, requires specific permissions, or has side effects like restarting services. This is adequate but not comprehensive.

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?

Very concise: two sentences describing purpose, then a bulleted list of argument explanations. Every sentence adds value; no fluff. Front-loaded with the key purpose.

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?

Given that an output schema exists (not shown), the description doesn't need to explain return values. It covers usage scenarios (setup, switching) and parameter details. It could mention validation or success indicators, but is mostly complete for a configuration 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?

Schema coverage is 0%, so the description compensates well. It explains that provider can be 'zotero' or 'mendeley', that api_key comes from a specific Zotero URL, user_id is numeric, and bibtex_path is for Mendeley. This adds meaning beyond the bare 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 configures the library provider for the Metis installation, with a specific verb (configure) and resource (library provider). It distinguishes from sibling tools like import_bibtex_library and sync_zotero_library which are related but different operations.

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

Usage Guidelines4/5

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

It explicitly says 'Call this during setup or when switching reference managers', providing clear context for when to use. It does not explicitly state when not to use it or list alternatives, but the guidance is sufficient.

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