Skip to main content
Glama

query_file_ownership

Read-only

Query Arch Linux file-package relationships to find package owners, list package files, or search across packages using specific modes.

Instructions

[ORGANIZATION] Unified tool for querying file-package ownership relationships. Supports three modes: 'file_to_package' (find which package owns a file), 'package_to_files' (list all files in a package with optional filtering), and 'filename_search' (search for files across all packages). Only works on Arch Linux. Examples: mode='file_to_package', query='/usr/bin/python' → returns 'python' package; mode='package_to_files', query='systemd', filter_pattern='.service' → lists all systemd service files; mode='filename_search', query='.desktop' → finds all packages with desktop entries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesQuery string: file path for file_to_package mode, package name for package_to_files mode, or filename pattern for filename_search mode
modeYesQuery mode: 'file_to_package' (find package owner), 'package_to_files' (list package files), or 'filename_search' (search across packages)
filter_patternNoOptional regex pattern to filter files (only used in package_to_files mode, e.g., '*.conf' or '/etc/')
Behavior4/5

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

Annotations indicate readOnlyHint=true, and the description adds valuable context beyond this: it specifies the tool is Arch Linux-specific, describes the three operational modes with examples, and clarifies that filter_pattern is optional and mode-specific. No contradictions with annotations.

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?

The description is front-loaded with the core purpose, followed by mode explanations and concrete examples. Every sentence adds value without redundancy, making it efficient and well-structured for quick understanding.

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?

For a read-only tool with no output schema, the description is largely complete: it covers purpose, usage, modes, and examples. However, it lacks details on return formats or error handling, which could aid the agent in interpreting results.

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%, providing full parameter documentation. The description adds meaning by explaining how query varies by mode and giving usage examples, but it doesn't significantly enhance the schema's details, meeting the baseline for high 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?

The description clearly states the tool's purpose as querying file-package ownership relationships with three specific modes, distinguishing it from siblings like search_aur or get_official_package_info by focusing on ownership mapping rather than package info or installation.

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?

It explicitly defines when to use each mode with examples (e.g., mode='file_to_package' for finding package owners), provides context (only works on Arch Linux), and implicitly distinguishes from siblings by its unique ownership query focus.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nihalxkumar/arch-linux-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server