Boosthis

Get Integration Kit

boosthis_get_integration_kit

Read-only

A Boosthis kit for THIS project - no upload; the single-use address needs no key, include_files no shell. Withheld reply? Same kit at GET https://www.boosthis.com/api/kit/ (project key as bearer). runtimes: every runtime this project has in ONE call, same key; runtime picks one, see enum. The reply carries file_list (path + sha256), version, kit_download_once_url; install_command adds typed commands. Writing the files is not the install: the kit is wired in, reporting switched on, and the app confirmed checked in.

Input Schema

TableJSON Schema

Name	Required	Description
`runtime`	No	Required. Which runtime kit to deliver. Boosthis names every runtime a project spans at https://www.boosthis.com/scan.
`runtimes`	No	The normal route: every runtime this project has in one call - an address each, not a kit's files.
`files_page`	No	Page of the by-value walk (guide parts, then files). Default 1; files_next_page names the next if any.
`project_code`	No	The 8-character code from this description's lead, not the name two projects can share. Account token only.
`include_files`	No	Send every kit file by value instead of the manifest, a page at a time. Only when no shell can be run.
`install_command`	No	Adds the typed download commands.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 22, 2026

changedInput schema / properties / files_page / description

Previous value: -"Page of the by-value walk (guide parts, then files). Default 1; files_next_page names the next while any remain."New value: +"Page of the by-value walk (guide parts, then files). Default 1; files_next_page names the next if any."

changedInput schema / properties / install_command / description

Previous value: -"Adds the typed download commands to the reply."New value: +"Adds the typed download commands."

changedInput schema / properties / runtimes / description

Previous value: -"Optional. Several runtimes in one call: one download address each, not one kit's files."New value: +"The normal route: every runtime this project has in one call - an address each, not a kit's files."

Changed4 schema fields changedSep 11, 2026

changedInput schema / properties / files_page / description

Previous value: -"Page of the by-value walk: guide parts first, then files. Defaults to 1; files_next_page names the next while any remain."New value: +"Page of the by-value walk (guide parts, then files). Default 1; files_next_page names the next while any remain."

changedInput schema / properties / include_files / description

Previous value: -"Send every kit file by value instead of the manifest, a page at a time. Needed only when a shell command cannot be run."New value: +"Send every kit file by value instead of the manifest, a page at a time. Only when no shell can be run."

changedInput schema / properties / project_code / description

Previous value: -"The 8-character project code from this description's lead - not the name, which two projects can share. Needed only with an account token."New value: +"The 8-character code from this description's lead, not the name two projects can share. Account token only."

changedInput schema / properties / runtimes / description

Previous value: -"Optional. Several runtimes in one call, for a project with more than one surface. The reply is one download address per runtime, not one kit's files."New value: +"Optional. Several runtimes in one call: one download address each, not one kit's files."

Changed3 schema fields changedSep 5, 2026

changedInput schema / properties / project_code / description

Previous value: -"The 8-character project code from this description's lead - not the name, which two projects can share. Only a caller using an account token needs it."New value: +"The 8-character project code from this description's lead - not the name, which two projects can share. Needed only with an account token."

changedInput schema / properties / runtimes / description

Previous value: -"Optional. Several runtimes in one call, for a project with more than one surface. The reply is one download address per runtime rather than one kit's files."New value: +"Optional. Several runtimes in one call, for a project with more than one surface. The reply is one download address per runtime, not one kit's files."

removedInput schema / properties / runtimes / items / enum

Removed value: -[
-  "rn",
-  "web",
-  "node",
-  "bun",
-  "python",
-  "java",
-  "go",
-  "php",
-  "dotnet",
-  "ruby",
-  "flutter",
-  "swift",
-  "kotlin",
-  "rust",
-  "elixir",
-  "edge"
-]

Changed1 schema field changedSep 4, 2026

changedInput schema / properties / project_code / description

Previous value: -"The 8-character project code from this description's lead - not the name, which two projects can share. Needed only by a caller using an account token, which names no project of its own."New value: +"The 8-character project code from this description's lead - not the name, which two projects can share. Only a caller using an account token needs it."

Changed5 schema fields changedSep 3, 2026

changedInput schema / properties / files_page / description

Previous value: -"Page of files[] when include_files is true. Defaults to 1; the reply carries files_next_page while more remain."New value: +"Page of the by-value walk: guide parts first, then files. Defaults to 1; files_next_page names the next while any remain."

removedInput schema / properties / include_guide

Removed value: -{
-  "description": "Add the written install guide. Left out by default: it is most of the reply's size. The kit address above serves it.",
-  "type": "boolean"
-}

changedInput schema / properties / project_code / description

Previous value: -"The 8-character project code from this description's lead — not the name, which two projects can share. Required if the account holds several projects."New value: +"The 8-character project code from this description's lead - not the name, which two projects can share. Needed only by a caller using an account token, which names no project of its own."

changedInput schema / properties / runtime / description

Previous value: -"Which runtime kit to deliver. Defaults to 'rn'. Boosthis names every runtime a project spans at https://www.boosthis.com/scan."New value: +"Required. Which runtime kit to deliver. Boosthis names every runtime a project spans at https://www.boosthis.com/scan."

addedInput schema / properties / runtimes

Added value: +{
+  "description": "Optional. Several runtimes in one call, for a project with more than one surface. The reply is one download address per runtime rather than one kit's files.",
+  "items": {
+    "enum": [
+      "rn",
+      "web",
+      "node",
+      "bun",
+      "python",
+      "java",
+      "go",
+      "php",
+      "dotnet",
+      "ruby",
+      "flutter",
+      "swift",
+      "kotlin",
+      "rust",
+      "elixir",
+      "edge"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

Changed5 schema fields changedSep 2, 2026

changedInput schema / properties / files_page / description

Previous value: -"Which page of files[] to send when include_files is true. Defaults to 1; keep calling with the next page while the reply carries files_next_page."New value: +"Page of files[] when include_files is true. Defaults to 1; the reply carries files_next_page while more remain."

changedInput schema / properties / include_files / description

Previous value: -"Send every kit file by value instead of the compact manifest. Needed only when a shell command cannot be run — the files then arrive a page at a time. The largest reply this tool produces, so the guide is added only if include_guide asks too."New value: +"Send every kit file by value instead of the manifest, a page at a time. Needed only when a shell command cannot be run."

changedInput schema / properties / include_guide / description

Previous value: -"Add the full written install guide to the reply. Left out by default: it is most of the reply's size and hosts withhold replies that large. The kit address above serves it too."New value: +"Add the written install guide. Left out by default: it is most of the reply's size. The kit address above serves it."

changedInput schema / properties / project_code / description

Previous value: -"The 8-character project code from this description's lead — not the project name, which two projects can share. Required when the account holds several projects."New value: +"The 8-character project code from this description's lead — not the name, which two projects can share. Required if the account holds several projects."

changedInput schema / properties / runtime / description

Previous value: -"Which runtime kit to deliver, matched to the project you are in. Defaults to 'rn' (React Native) when omitted. Boosthis names every runtime a project spans at https://www.boosthis.com/scan."New value: +"Which runtime kit to deliver. Defaults to 'rn'. Boosthis names every runtime a project spans at https://www.boosthis.com/scan."

Changed1 schema field changedSep 1, 2026

changedInput schema / properties / runtime / description

Previous value: -"Which runtime kit to deliver, matched to the project you are in. Defaults to 'rn' (React Native) when omitted."New value: +"Which runtime kit to deliver, matched to the project you are in. Defaults to 'rn' (React Native) when omitted. Boosthis names every runtime a project spans at https://www.boosthis.com/scan."

Changed3 schema fields changedAug 31, 2026

changedInput schema / properties / include_files / description

Previous value: -"Send every kit file by value instead of the compact manifest. Needed only when a shell command cannot be run — the files then arrive a page at a time. This is the largest reply this tool produces, so the guide is not added unless include_guide asks for it too."New value: +"Send every kit file by value instead of the compact manifest. Needed only when a shell command cannot be run — the files then arrive a page at a time. The largest reply this tool produces, so the guide is added only if include_guide asks too."

changedInput schema / properties / include_guide / description

Previous value: -"Add the full written install guide to the reply. It is left out by default because it is most of the reply's size and hosts withhold replies that large; the same text is also served at the plain-HTTPS kit address."New value: +"Add the full written install guide to the reply. Left out by default: it is most of the reply's size and hosts withhold replies that large. The kit address above serves it too."

changedInput schema / properties / project_code / description

Previous value: -"Confirms which project this install belongs to. The exact project code or project name is accepted, case-insensitively."New value: +"The 8-character project code from this description's lead — not the project name, which two projects can share. Required when the account holds several projects."

Changed1 schema field changedAug 31, 2026

addedInput schema / properties / install_command

Added value: +{
+  "description": "Adds the typed download commands to the reply.",
+  "type": "boolean"
+}

First observedAug 29, 2026

TDQS

A3.9/5.0

Behavior5/5

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

The annotations only say readOnlyHint and openWorldHint, so the description carries the burden of explaining behavior. It adds valuable context: the operation involves no upload, addresses are single-use and need no key, `install_command` adds typed commands, and writing files alone does not constitute installation. The 'kit is wired in, reporting switched on, and the app confirmed checked in' line gives an agent a clearer mental model of what receiving a kit means.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and information-dense, and most sentences contribute content. However, it reads as cryptic and telegraphic ('no upload; the single-use address needs no key, include_files no shell', 'Withheld reply?'), which harms quick comprehension. It is not poorly sized, but it is not cleanly front-loaded or easily scannable.

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?

Despite having no output schema, the description enumerates the key response fields (file_list, version, kit_download_once_url) and addresses special cases like no shell and multiple runtimes. The main gaps are the ambiguous meaning of `runtimes` ('an address each, not a kit's files') and the unexplained 'Withheld reply?' fallback, but overall an agent has enough orientation to invoke and interpret the result.

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 a baseline of 3 applies. The description goes beyond the schema by distinguishing `runtime` (pick one) from `runtimes` (all in one call), explaining `include_files` as a no-shell fallback, and clarifying that `install_command` adds typed download commands. `files_page` and `project_code` are not elaborated, but the schema already documents them fully.

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 makes clear this tool fetches a Boosthis integration kit for the current project, distinct from removal or verification kits. It even sketches what the reply contains (file_list, version, kit_download_once_url), so an agent can tell this is a delivery/retrieval tool. It loses a point because the phrasing is awkward and some statements ('an address each, not a kit's files') muddy rather than sharpen the core purpose.

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?

There is implied guidance for choosing `runtime` versus `runtimes` and for using `include_files` only when no shell can be run. However, the description never explicitly contrasts this tool with alternatives like `get_removal_kit` or `verify_kit_install`, nor states when to prefer the direct GET fallback beyond the cryptic 'Withheld reply?'.

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

All Boosthis tools Inspect

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

Need Help?