Skip to main content
Glama

Boosthis

by com.boosthis
OverviewDiscussionsAdmin

What Should I Look At Next

boosthis_what_should_i_look_at_next
Read-only

A triage ordering: the worst-rated and slowest screens first, each with a one-line reason. No read credentials: a dashboard pointer, never empty. Read-only. More projects: your_projects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
projectNoDashboard name, 'name (runtime)' or install id; needs account_token. Default: newest reporter.
install_idNoInstall id (Connect AI card).
read_tokenNoRead-only token, same card.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / install_id / description
      Previous value: -"Install id (dashboard card)."New value: +"Install id (Connect AI card)."
  2. Changed1 schema field changed
    • changedInput schema / properties / project / description
      Previous value: -"Project to read: dashboard name, 'name (runtime)' or install id; needs account_token, else the newest reporter."New value: +"Dashboard name, 'name (runtime)' or install id; needs account_token. Default: newest reporter."
  3. Changed2 schema fields changed
    • changedInput schema / properties / install_id / description
      Previous value: -"Install id, from the dashboard card."New value: +"Install id (dashboard card)."
    • changedInput schema / properties / project / description
      Previous value: -"Project to read: dashboard name, 'name (runtime)', or install id. Needs account_token; absent, the most recent reporter."New value: +"Project to read: dashboard name, 'name (runtime)' or install id; needs account_token, else the newest reporter."
  4. Changed2 schema fields changed
    • changedInput schema / properties / install_id / description
      Previous value: -"Install id, from the project's dashboard card."New value: +"Install id, from the dashboard card."
    • changedInput schema / properties / read_token / description
      Previous value: -"Read-only token for it, from the same card."New value: +"Read-only token, same card."
  5. Changed3 schema fields changed
    • changedInput schema / properties / install_id / description
      Previous value: -"Optional: the install id to read live data for. On the HOSTED Boosthis MCP, copy it from the in-app dashboard's \"Connect your AI\" card and pass it here. Omit on a local stdio server (it uses BOOSTHIS_INSTALL_ID from the env)."New value: +"Install id, from the project's dashboard card."
    • changedInput schema / properties / project / description
      Previous value: -"Which project in the account to read — its dashboard name, that name with a runtime as 'name (runtime)', or an install id. Only meaningful with account_token."New value: +"Project to read: dashboard name, 'name (runtime)', or install id. Needs account_token; absent, the most recent reporter."
    • changedInput schema / properties / read_token / description
      Previous value: -"Optional: the SELF-scoped read token for that install (paired with install_id). It is read-only — it can read this app's own perf data but CANNOT delete it. Copy it from the in-app dashboard. Omit on a local stdio server (it uses BOOSTHIS_READ_TOKEN from the env)."New value: +"Read-only token for it, from the same card."
  6. Changed1 schema field changed
    • changedInput schema / properties / project / description
      Previous value: -"Which project in the account to read — its name as shown on the Boosthis dashboard (for example 'Rival Web'), a specific runtime of it as 'name (runtime)', or an install id. A project measured in several runtimes answers with its most recent one and names the others in `your_projects`. Only meaningful with account_token; absent, the answer is whichever project reported most recently."New value: +"Which project in the account to read — its dashboard name, that name with a runtime as 'name (runtime)', or an install id. Only meaningful with account_token."
  7. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark it read-only, and the description reinforces that while adding useful behavior: no credentials required, results are never empty, and output is a prioritized list with reasons. It does not discuss limits or project defaults, but it gives meaningful behavior beyond the annotations.

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?

Three short sentences carry the purpose, behavioral guarantees, and a pointer to an alternative with no wasted words. The most decision-relevant information is front-loaded.

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 simple read-only dashboard tool with no output schema, the description supplies the essential return shape (ordered screens with one-line reasons) and the no-credentials guarantee. It is slightly terse about limit and project selection, but the schema fills those gaps.

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?

With 75% schema coverage, most parameters are already documented. The description adds an important clarification that no read credentials are required despite a read_token parameter, and the pointer to your_projects helps with interpreting project scope. The limit parameter remains undocumented in prose, but its default/min/max constraints compensate.

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?

The description names the exact resource: a triage ordering of the worst-rated and slowest screens, with one-line reasons. This scope distinguishes it from the sibling tools, which target alerts, crash risk, exposure, or maintenance, without needing to open their schemas.

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 context is implied: it is a read-only dashboard pointer that needs no read credentials and never returns empty. The only explicit alternative routing is 'More projects: your_projects,' but there are no stated when-not-to-use conditions or comparisons to other sibling tools.

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