Goodeye

get_skill_files

Read-only

Fetch multiple files from a skill version's file tree in a single call.

paths is a list of relative paths, each of which must exactly match a row in the skill's file manifest (use get_skill to see the manifest). Envelopes are returned in lexicographic path order.

Each envelope carries the same fields as get_skill_file. Unknown paths appear as per-path error: "not_found" envelopes rather than failing the whole request. Once the aggregate inline budget is exhausted, remaining inline-eligible files are returned as error: "batch_response_cap_exceeded" references with no content. Every requested path appears exactly once in the response.

Requires view access on the skill. Returns {"files": [...]}.

Input Schema

TableJSON Schema

Name	Required	Description
`paths`	Yes	List of relative paths to fetch in one call.
`version`	No	Pin to a specific version number; omit to use the latest version.
`skill_id`	Yes	The skill to act on, identified by its UUID, slug, or name.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedJul 18, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Details error handling for unknown paths and budget exhaustion, ordering, and guarantee every path appears once. Annotations confirm read-only, and description adds significant behavioral 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?

Well-structured, front-loaded with purpose, each sentence adds value without redundancy.

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?

Comprehensive coverage of return format, error modes, ordering, and budget limits; output schema exists but description still clarifies structure.

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 covers 100% of parameters with descriptions; description adds practical context (e.g., paths must match manifest entries, version omitted uses latest, skill_id accepts UUID/slug/name).

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?

The description clearly states it fetches multiple files from a skill version's file tree, distinguishing from siblings like get_skill and get_skill_file.

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?

Explains inputs (paths must match manifest) and suggests using get_skill to see the manifest, but could be more explicit about when to use this vs. get_skill_file.

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

All Goodeye tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.