Skip to main content
Glama
Sign In
io.github.norrietaylor/distillery-mcp

io.github.norrietaylor/distillery-mcp

Official
by norrietaylor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

distillery_get

Retrieve a knowledge entry's full content and metadata by its unique ID. Use after locating an entry via search or list to get complete details.

Instructions

Retrieve a single knowledge entry by its unique ID.

USE WHEN: fetching the full content and metadata of a specific entry (e.g. after finding its ID via search or list).

PARAMS:

  • entry_id (str, required): UUID of the entry to retrieve.

RETURNS (success): { id: str, content: str, entry_type: str, ... } RETURNS (error): { error: true, code: "NOT_FOUND" | "INTERNAL", message: "..." }

RELATED: distillery_search (to find entries by content), distillery_list (to browse entries by filters)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entry_id": "<entry_id>"
    },
    "name": "distillery_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
entry_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A4.8/5.0
Behavior4/5

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

With no annotations, the description must disclose behavior. It does so by specifying the return structure for both success (id, content, entry_type) and error (code, message). While 'Retrieve' implies a read-only operation, it does not explicitly state that no mutation occurs, but the provided return/error formats give substantial behavioral insight for a simple GET.

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?

Well-structured with clear sections (USE WHEN, PARAMS, RETURNS, RELATED), front-loading the purpose. Every sentence provides essential information without redundancy. The format is scannable for an agent and not overly verbose.

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?

For a single-parameter retrieval tool with no output schema and no annotations, the description is complete. It covers when to use it, the parameter meaning, expected return types, and error handling, and even suggests sibling tools for related use cases. Nothing an agent needs to call it correctly is missing.

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

Parameters5/5

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

The description adds meaning beyond the schema by explaining that entry_id is a 'UUID of the entry to retrieve.' The schema only defines it as a string, so this clarifies the expected format and purpose, fully compensating for the 0% schema description coverage.

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 ('Retrieve') and resource ('knowledge entry') with a unique ID, clearly distinguishing from siblings like distillery_search and distillery_list. The description explicitly notes the tool retrieves a single entry by ID, which is unambiguous.

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?

Provides an explicit 'USE WHEN' section that tells the agent exactly when to use this tool (fetching full content/metadata of a specific entry). It also lists related tools (search, list) as alternatives, giving clear routing context without needing to inspect other schemas.

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