Skip to main content
Glama

Boosthis

by com.boosthis
OverviewDiscussionsAdmin

Snapshot

boosthis_snapshot
Read-only

The latest upload from one install: per-route rows, per-screen diagnosis, summary and budgets where present. section takes a page section (incl. coverage) or all; an empty one names its silence, not a clean result. No credentials or none uploaded: a dashboard pointer. Read-only. More projects: your_projects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectNoDashboard name, 'name (runtime)' or install id; needs account_token. Default: newest reporter.
sectionNo
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
    • addedInput schema / properties / section
      Added value: +{
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / install_id / description
      Previous value: -"Install id (dashboard card)."New value: +"Install id (Connect AI card)."
  3. 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."
  4. 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."
  5. 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."
  6. 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."
  7. 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."
  8. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations provide readOnlyHint=true and openWorldHint=false, so the description doesn't need to repeat that. It adds value by disclosing the edge case behavior: 'an empty one names its silence, not a clean result' and 'No credentials or none uploaded: a dashboard pointer.' This explains what happens in specific scenarios, beyond just read-only. It doesn't contradict annotations, so no flag.

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 about three sentences and covers a lot of ground: data contents, section parameter behavior, edge cases, and a hint for multiple projects. It's front-loaded with the main purpose. The sentence 'an empty one names its silence, not a clean result' is a bit cryptic and could be clearer, but overall it's efficient and not overly verbose.

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?

With readOnlyHint=true, no output schema, and a relatively simple parameter set, the description covers the key aspects: data contents, section semantics, and edge cases. It could mention that the response is a summary or that no credentials can still return a pointer, but it already hints at that. The description is sufficient for an agent to call it correctly without additional context.

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 schema description coverage is 75%, leaving the 'section' parameter with no description. The description explains 'section takes a page section (incl. coverage) or `all`', which adds critical meaning for that uncovered parameter. For the other parameters, the schema already has descriptions, but the description doesn't add more detail beyond what's in the schema. This compensates well for the gap.

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 says 'latest upload from one install: per-route rows, per-screen diagnosis, summary and budgets where present,' which clearly identifies the resource and what data it returns. It distinguishes itself from siblings like 'project_diary' and 'session_summary' by focusing on the latest upload snapshot. However, it doesn't explicitly name a sibling as an alternative, so it's not fully distinct.

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?

It gives a clear condition: 'No credentials or none uploaded: a dashboard pointer,' which tells the agent when the tool returns a different result. It also mentions 'More projects: `your_projects`' as a pointer for project selection. However, it doesn't explicitly say when NOT to use this tool or name an alternative sibling for different use cases, so it's not fully explicit.

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