Skip to main content
Glama

librarian_status

Returns the most recent Librarian run report: step results, health checks, and count of pending proposals. Read-only; changes nothing.

Instructions

Report from the most recent Librarian run: what each step did, the health checks, and how many proposals are waiting. Changes nothing; the Librarian itself is started on a schedule with enigma-mcp librarian.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does substantial work: 'Changes nothing' declares the read-only, non-mutating nature, which is the single most important trait for a status tool. It also discloses that the Librarian runs on an external schedule rather than being invocable here, and enumerates the content of the report. Missing only side details such as what is returned if no Librarian run has ever occurred.

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?

Two short clauses, front-loaded with what the report contains, followed by the behavioral caveat and the scheduling note. Every element earns its place: the payload enumeration sets expectations and the second clause prevents a mis-invocation. No filler or restatement of the title.

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 zero-parameter, read-only status tool with no output schema and no annotations, the description supplies enough: what the report contains, that nothing is mutated, and where the underlying process comes from. Since there is no output schema, a slightly more concrete sketch of the return shape (e.g. empty-state behavior) would fully close the gap.

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?

The tool takes zero parameters, so there is no parameter semantics to add meaning to and the baseline of 4 applies. The description correctly signals a parameterless call by describing a single fixed report rather than implying filters or options.

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?

Names a specific resource and output: the report from the most recent Librarian run, covering per-step actions, health checks, and pending proposal counts. That is far more specific than a tautology, and no sibling tool in the catalog covers Librarian status, so the risk of confusion is low. It stops short of explicitly contrasting with nearby tools like graph_stats or list_tasks, which is the only thing keeping it from a 5.

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?

The clause 'the Librarian itself is started on a schedule with enigma-mcp librarian' gives clear guidance on a real failure mode: the agent should not look for a way to trigger a run through this tool. It implies the when-to-use context (checking on background maintenance and pending proposals) without stating it as an explicit trigger condition or naming alternatives, so it is clear context rather than full when/when-not guidance.

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