Skip to main content
Glama

distill_capabilities

Report versions, limits, and available features (LibreOffice, LLMLingua-2) to verify local document conversion options.

Instructions

Report versions, limits and available features (LibreOffice, LLMLingua-2)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
linguaYes
versionYes
maxBytesYes
libreofficeYes
liteparseVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it does signal a read-only informational operation with no side effects by framing it as a 'report'. It says nothing about permissions, cost, or whether the capability list can change between calls, though the risk profile of a zero-parameter read is low.

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?

A single front-loaded sentence with no filler, and the key nouns come early. It is close to over-terse, since 'limits' is left unelaborated, but nothing is wasted.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and with no parameters the calling surface is trivial. What is missing is any framing of what 'limits' covers and when in a workflow an agent should call this, leaving the description minimally adequate rather than complete.

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?

There are zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the parenthetical component names add mild framing but no parameter meaning is required.

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?

The description names a specific verb ('Report') and a concrete set of resources ('versions, limits and available features'), including the two underlying components (LibreOffice, LLMLingua-2). It is clear what the tool returns, but it makes no effort to distinguish itself from the sibling distill_file/distill_files tools.

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?

Usage is only implied: the reader can infer this is an introspection/capability-discovery call to make before relying on other features. There is no explicit when-to-use statement, no prerequisite or ordering advice, and no mention of alternatives.

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