Skip to main content
Glama

get_boards

List tracked single-board computers and mini PCs with specs and current best vendor prices, filtering by brand or family to compare hardware options and find the lowest price.

Instructions

List tracked boards with specs and current best vendor price.

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": "get_boards"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNo
limitNo
familyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations at all, the description carries full behavioral burden, and it discloses little beyond the data fields: no authentication requirements, no pagination or default-limit behavior (limit defaults to 20 per the schema), and no statement about whether the price shown is cached or live. Since an output schema exists, return shape is out of scope, but operational behavior remains unexplained.

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?

A single front-loaded sentence with no filler, which is structurally clean. Its brevity edges into under-specification, but nothing in the sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema covers return values, but with zero annotation coverage, three undocumented parameters, and no usage guidance, the definition leaves an agent guessing about filtering behavior and how this listing differs from get_board_history or get_deals.

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

Parameters2/5

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

Schema description coverage is 0% for three parameters (brand, family, limit), and the description adds nothing about any of them — no filtering semantics, no wildcard/partial-match rules, no behavior when a filter matches nothing. Only the generic concept of "tracked boards" is conveyed.

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?

The description gives a specific verb ("List") and resource ("tracked boards") plus the payload ("specs and current best vendor price"), which is enough for an agent to know what it retrieves. It does not distinguish itself from get_board_history or get_deals, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no pointer to alternatives such as get_board_history for historical data. The only contextual cue is the word "tracked", which implies a scope but not a routing rule.

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