Skip to main content
Glama

Read an entry and its supporting files

get_entry_bundle
Read-onlyIdempotent

Read an entry along with its supporting files, such as reference documents or scripts, in one request. Use it when you need more than the entry itself.

Instructions

Read one entry together with the files that belong to it, such as reference documents or scripts. Not covered by get_entry, which returns only the entry itself.

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": {
      "id": "<id>"
    },
    "name": "get_entry_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEntry id or name.
max_filesNoMaximum supporting files to include.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and not repeated here. The description usefully adds the return scope (entry plus associated files, with example file types), but says nothing about how many files are returned by default, ordering, or truncation behavior tied to max_files.

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 sentences, zero filler: the core action is front-loaded and the disambiguation from get_entry follows immediately. Every clause earns its place.

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?

With no output schema, the description should sketch what comes back, and it does — the entry plus its supporting files with concrete examples. For a simple two-parameter read-only tool this is close to complete; only default file-inclusion behavior and max_files effects are left unstated.

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

Parameters3/5

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

Schema description coverage is 100%, so 'id' and 'max_files' are already documented including the 1-50 range. The description adds only indirect meaning ('one entry' implies the id, 'the files that belong to it' implies the file collection) and never mentions max_files or what happens when the cap is hit, so the baseline 3 applies.

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 entry together with the files that belong to it') and bounds the resource with concrete examples (reference documents, scripts). It also explicitly distinguishes itself from get_entry, so an agent can choose between the two without opening either schema.

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 second sentence names the alternative (get_entry) and the condition that separates them: get_entry returns only the entry, this one returns the entry plus its files. That conveys when to pick this tool, though it stops short of an explicit 'use this when you need supporting files' instruction or any exclusions beyond the sibling comparison.

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