Skip to main content
Glama

Search Systems

search_systems
Read-only

Search Beaker systems by CPU, architecture, memory, pool, and owner. Combine filters with AND logic to find matching systems.

Instructions

Search Beaker systems by hardware attributes and ownership.

Find systems matching CPU, architecture, memory, pool, owner, and other criteria. All filters are combined with AND logic.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
archNoArchitecture filter: 'x86_64', 'aarch64', 's390x', 'ppc64le'.
poolNoBeaker pool name, e.g. 'rhelvirt-gating'.
userNoCurrent user (reserved by) username to filter by. Shows systems currently reserved by this user.
limitNoMaximum number of systems to return. Default: 10.
ownerNoOwner username to filter by, e.g. 'tasharma'. Exact match.
memoryNoMemory in MiB. Prefix with >= or <= for range, e.g. '>=131072' for 128GB+.
statusNoSystem status: 'Automated', 'Manual', 'Broken', or '' for any. Default: 'Automated'.Automated
cpu_coresNoCPU core count. Prefix with >= or <= for range, e.g. '>=64'.
cpu_modelNoCPU model number identifying microarchitecture. Intel family 6: 207=Emerald Rapids, 175=Sierra Forest, 173=Granite Rapids, 143=Sapphire Rapids, 106=Ice Lake, 85=Skylake/Cascade Lake, 79=Broadwell, 63=Haswell, 165=Comet Lake. AMD family 25: 17=Genoa, 1=Milan. AMD family 23: 49=Rome, 1=Naples. AMD family 26: Turin.
loaned_toNoUsername the system is loaned to. Shows systems currently loaned to this user.
cpu_familyNoCPU family number. Intel=6, AMD Zen3/4=25, AMD Zen1/2=23, AMD Zen5=26.
cpu_vendorNoCPU vendor string, e.g. 'GenuineIntel', 'AuthenticAMD', 'Ampere(R)'.
cpu_model_nameNoCPU model name substring to match, e.g. 'Xeon Gold'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already declare readOnlyHint=true. The description adds that filters combine with AND logic, but does not disclose other behavioral traits (e.g., pagination, rate limits, empty result handling). The added context is minimal but non-contradictory.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with purpose, and efficient. It could be slightly more compact but effectively communicates the tool's role without redundancy.

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?

Given 13 parameters fully documented in the schema and an existing output schema, the description is sufficient. It does not cover error conditions or alternative usage patterns, but the schema and annotations fill most gaps.

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 all 13 parameters are documented. The description lists categories (hardware attributes, ownership) but adds no significant detail beyond the schema. Baseline 3 is appropriate.

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 verb 'Search' and resource 'Beaker systems'. It lists specific attributes (CPU, architecture, memory, pool, owner) and notes AND logic, distinguishing it from siblings like list_systems (unfiltered listing) and get_system_details (single system).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for searching by hardware attributes and ownership, but does not explicitly state when to use this tool versus alternatives (e.g., list_systems for unfiltered listing). No when-not or alternative guidance is provided.

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/faizbawa/mcp-beaker'

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