Skip to main content
Glama
bunkerity

BunkerWeb MCP

Official
by bunkerity
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

cache_fetch_file

Read-only

Read a scheduler job cache file by plugin, job, and file name; returns printable text or base64 bytes when download is true. Use cache_list to locate files.

Instructions

Read one job cache file, keyed as listed by cache_list. Returns printable text, or base64 bytes with download=true. Use cache_list to find files.

Input Schema

NameRequiredDescriptionDefault
pluginYesPlugin ID that owns the file, as listed by cache_list
serviceNoService ID that owns the file; omit for global
downloadNoTrue returns the raw bytes as data_base64; false returns JSON with printable text only
job_nameYesJob that wrote the file, as listed by cache_list
file_nameYesFile name, as listed by cache_list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.6.0
    • addedInput schema / properties / download / description
      Added value: +"True returns the raw bytes as data_base64; false returns JSON with printable text only"
    • addedInput schema / properties / file_name / description
      Added value: +"File name, as listed by cache_list"
    • addedInput schema / properties / job_name / description
      Added value: +"Job that wrote the file, as listed by cache_list"
    • addedInput schema / properties / plugin / description
      Added value: +"Plugin ID that owns the file, as listed by cache_list"
    • addedInput schema / properties / service / description
      Added value: +"Service ID that owns the file; omit for global"
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, and the description adds real behavioral detail beyond it: the return is printable text by default or base64 bytes when download=true. It does not cover error cases (missing file, permission) but adds substantive context.

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?

Three short sentences, front-loaded with the action and the key semantics, with zero filler.

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?

Read-only, no output schema, so the description carrying the return-value distinction (text vs base64) is exactly what's needed. Minor gaps around file-not-found behavior keep it from a 5.

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 100%, so baseline is 3, and the description reinforces the download flag's effect on return type beyond the schema wording. The plugin/service/job_name/file_name keying is only restated, so it doesn't lift this to 5.

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 and resource ('Read one job cache file') and immediately scopes it against the listing sibling. An agent can distinguish it from cache_list and cache_delete_file from the description alone.

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?

Explicitly routes the agent to cache_list to discover file keys, which is the required prerequisite for all three required params. It does not spell out when-not to use it (e.g., it is not for jobs/configs), but the usage context is clear.

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