Skip to main content
Glama

list_backends

Lists installed and planned FPGA add-ons with the part families each covers and its state, helping verify available toolchain support.

Instructions

List the installed and planned FPGA add-ons, the part families each covers, and its state.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; the word "List" implies a read-only, non-mutating operation and the text sketches the returned fields (part families, state), which is useful. However it does not clarify what "planned" means (pending requests vs. pre-announced support) or how state is represented, leaving ambiguity for a tool with no annotation safety profile.

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?

A single compact sentence with the verb and object front-loaded and zero filler. Nothing is repeated from structured fields and nothing could be cut without losing 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 no-parameter enumeration tool with no output schema, the description supplies what the agent needs: what is listed and what each item includes. Its residual gap is terminology ("planned" and "state") that an agent would have to interpret on first call.

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?

The tool takes zero parameters, so there is no parameter meaning to add; baseline for a parameterless tool applies. The description correctly avoids inventing arguments.

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?

Uses a specific verb ("List") and disambiguates the jargon term "backends" into concrete objects: installed and planned FPGA add-ons. It also names what each entry carries (part families, state), so an agent knows this is a discovery/enumeration tool rather than a control tool. It stops short of naming a sibling to contrast with.

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 only implied: an agent can infer this is the entry point for seeing what add-ons exist before acting via backend_control or install_status, but the description never states when to prefer it over those siblings or that it takes no filters. No when-not guidance is offered.

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