Skip to main content
Glama

Check PC build compatibility

check_build
Read-onlyIdempotent

Check whether PC parts fit together (socket, chipset, RAM type, case and cooler clearance, power) and get the recommended PSU wattage. CPU and GPU can be catalog model names or slugs; any part can be a listing id from search_listings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpuNo
gpuNo
psuNoListing id
ramNoListing id
caseNoListing id
coolerNoListing id
storageNoListing id
motherboardNoListing id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already establish the safety profile (readOnlyHint=true, idempotentHint=true, openWorldHint=false), so the bar is lower. The description does add real behavioral content by naming the checks performed and disclosing that a wattage recommendation is returned, but it says nothing about how conflicts are reported or how unknown/unmatched parts are handled.

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 dense sentences with the validation scope front-loaded and the accepted identifier formats second. No filler, no restatement of the tool name, and every clause conveys actionable information.

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 covers what is evaluated and one key return value (recommended PSU wattage). The remaining gap is input-shape guidance — all eight parameters are optional, and the description never says whether a two-part check is valid or where the minimum threshold lies.

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 75%, with six parameters documented only as 'Listing id' and cpu/gpu undocumented. The description fills exactly that gap by stating CPU and GPU accept catalog model names or slugs and that any part can take a listing id from search_listings, resolving the main ambiguity. It does not clarify that all eight parameters are optional or what the minimum viable input is.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'check whether PC parts fit together' — and enumerates the exact compatibility dimensions (socket, chipset, RAM type, clearance, power), plus the secondary outcome of a recommended PSU wattage. It does not explicitly contrast itself with siblings like estimate_fps or find_models, so an agent must infer that this is the assembly-validation tool.

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?

Usage is implied rather than stated: the description assumes the agent already has candidate parts in hand and points to search_listings as the source of listing ids. There is no explicit 'when to use this vs. X' guidance, no statement that it validates a hypothetical build rather than an existing listing, and no note on what happens with partial input.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources