Skip to main content
Glama

Boosthis

by com.boosthis
OverviewDiscussionsAdmin

Which Kits

boosthis_which_kits
Read-only

Which Boosthis kits this project needs, from manifest file names visible in it - nothing downloaded or executed. The inventory step before boosthis_get_integration_kit, whose runtimes list takes them all at once. Names the kit each file implies, what is already registered under this key, and the files whose contents decide one. With no arguments: the signal table.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filesNoManifest files visible in the project: path (project-relative, e.g. apps/api/package.json) and dependencies (names read out of it, where contents decide the kit - empty means none found, omitted means not read).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / files / description
      Previous value: -"Optional. Manifest files visible in the project: path (project-relative, e.g. apps/api/package.json) and dependencies (names read out of it, where contents decide the kit - empty means none found, omitted means not read)."New value: +"Manifest files visible in the project: path (project-relative, e.g. apps/api/package.json) and dependencies (names read out of it, where contents decide the kit - empty means none found, omitted means not read)."
  2. Changed3 schema fields changed
    • changedInput schema / properties / files / description
      Previous value: -"Optional. Manifest files visible in the project, each as {path, dependencies}."New value: +"Optional. Manifest files visible in the project: path (project-relative, e.g. apps/api/package.json) and dependencies (names read out of it, where contents decide the kit - empty means none found, omitted means not read)."
    • removedInput schema / properties / files / items / properties / dependencies / description
      Removed value: -"Names read out of that file, where its contents decide the kit. An empty list means read and none found; omitting it means not read."
    • removedInput schema / properties / files / items / properties / path / description
      Removed value: -"Project-relative path, such as apps/api/package.json."
  3. Changed1 schema field changed
    • changedInput schema / properties / files / items / properties / dependencies / description
      Previous value: -"Names read out of that file, where its contents decide the kit. An empty list says it was read and names none; omitting it says the contents were not read."New value: +"Names read out of that file, where its contents decide the kit. An empty list means read and none found; omitting it means not read."
  4. Changed3 schema fields changed
    • changedInput schema / properties / files / description
      Previous value: -"Optional. Manifest files visible in the project, each as {path, dependencies}. Dependency names matter only where a file's contents decide the kit, as a package.json does."New value: +"Optional. Manifest files visible in the project, each as {path, dependencies}."
    • changedInput schema / properties / files / items / properties / dependencies / description
      Previous value: -"Dependency or plugin names read out of that file, where its contents decide which kit it means. An empty list reads as a file that was read and names none, which is a Node service or a JVM server; leaving it out says the contents were not read."New value: +"Names read out of that file, where its contents decide the kit. An empty list says it was read and names none; omitting it says the contents were not read."
    • changedInput schema / properties / files / items / properties / path / description
      Previous value: -"Project-relative path of the manifest file, such as apps/api/package.json."New value: +"Project-relative path, such as apps/api/package.json."
  5. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description reinforces them with "nothing downloaded or executed" and, more valuably, describes what the call returns (implied kit per file, current registration under this key, files whose contents decide one) despite there being no output schema.

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 core purpose and the sibling relationship are front-loaded, and there is no filler. The middle sentence is a dense, fragmentary list that takes a re-read, but every clause carries load.

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 single-optional-parameter tool with no output schema, the description covers purpose, sequencing, read-only behavior, and the shape of the return. Nothing essential is missing, though the exact output structure remains only loosely characterized.

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 100%, so the `files` array and its path/dependencies fields are fully documented in the schema (baseline 3). The description adds value beyond it by noting the no-argument behavior (signal table) and that omitted dependencies means "not read" versus empty meaning "none found."

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?

States a specific outcome: which Boosthis kits the project needs, derived from manifest file names. It distinguishes itself from the sibling boosthis_get_integration_kit by naming it as the following step, so an agent can place it without opening either schema.

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

Usage Guidelines4/5

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

"The inventory step before boosthis_get_integration_kit, whose `runtimes` list takes them all at once" clearly positions when to use this versus the sibling that consumes its output, and "With no arguments: the signal table" notes a distinct invocation mode. No explicit exclusion conditions, but the sequencing guidance is strong.

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

All Boosthis toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources