Skip to main content
Glama

report

Summarises FPGA build outputs, including utilisation, timing, failing constraints, and bitstream details, from a specified folder and auto-detects the producing backend.

Instructions

Summarise the reports in a build output folder: utilisation, timing, failing constraints, bitstream.

backend: the add-on that produced the folder; detected automatically when omitted.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "outputs_dir": "<outputs_dir>"
    },
    "name": "report"
  }
}

Input Schema

NameRequiredDescriptionDefault
backendNo
outputs_dirYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only summarisation but does not confirm that it is non-destructive, state what happens if outputs_dir is missing or malformed, describe return format, or clarify whether backend detection can fail. It does add the useful behavior that backend is auto-detected when omitted.

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 tight sentences with the primary purpose front-loaded, followed by parameter-specific behavior. There is little wasted wording, though the trailing newline and lack of explicit separation between summary behavior and parameter notes are minor blemishes.

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

Completeness3/5

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

For a read-only reporting tool with no output schema and no annotations, the description covers the main content of the summary and explains the optional backend behavior. It remains incomplete regarding error handling, output structure, and when to prefer sibling tools, which leaves an agent with some ambiguity about call context and failure cases.

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 0%, so the description must compensate. It partially does by explaining that backend defaults to automatic detection when omitted and by making outputs_dir's meaning clear through the overall purpose. However, it does not describe expected path format, valid backend names, or what detection does when it cannot identify the backend.

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 names a specific verb ("Summarise") and resource ("reports in a build output folder"), and enumerates the summary contents (utilisation, timing, failing constraints, bitstream). It is clearly distinguishable from siblings such as build_status or activity, though it does not explicitly state how it differs from them.

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 explicit when-to-use or when-not-to-use guidance, and no alternatives are named. The purpose implies it should be used after a build produces outputs, but the agent must infer that context and cannot tell from the description whether build_status or dashboard_info would be more appropriate for certain questions.

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