Skip to main content
Glama

Boosthis

by com.boosthis
OverviewDiscussionsAdmin

Full Stack Trace

boosthis_full_stack_trace
Read-only

One user action across the stack as a nested waterfall of spans (layer, route label, duration, start offset, rating), each under the call that caused it; criticalHop names the hop responsible for the end-to-end time, not just the longest. Relative timings, code-defined labels only. A read token sees one install, account_token the whole chain. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
trace_idNoOne trace by id (32 hex, from the trace page). Absent: the latest.
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. Changed2 schema fields changed
    • changedInput schema / properties / install_id / description
      Previous value: -"Install id, from the dashboard card."New value: +"Install id (dashboard card)."
    • addedInput schema / properties / trace_id
      Added value: +{
+  "description": "One trace by id (32 hex, from the trace page). Absent: the latest.",
+  "type": "string"
+}
  3. 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."
  4. Changed2 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 / 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."
  5. First observed

TDQS

A4/5.0
Behavior5/5

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

The readOnlyHint already covers safety, and the description adds meaningful behavioral detail: criticalHop identifies the hop responsible for end-to-end time, timings are relative, labels are code-defined, and token choice changes visibility from one install to the whole chain. There is no contradiction with 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?

The main output semantics are front-loaded, and each sentence adds a distinct piece of information: output shape, criticalHop meaning, timing/label constraints, token scope, and read-only status. There is no filler repetition.

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 no output schema, the description does a strong job explaining what the response contains and how to interpret criticalHop. Minor gaps remain, such as not clarifying how account_token is supplied or whether any time units apply, but the input schema covers invocation details sufficiently.

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 100%, so the schema already documents trace_id, install_id, and read_token. The description adds token-scope context but does not deepen per-parameter semantics, so the baseline of 3 is appropriate.

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 clearly defines the tool's output: a nested span waterfall for one user action, with criticalHop semantics and explicit span fields. It is specific enough to distinguish from most siblings, though it lacks an explicit action verb and does not name a sibling for contrast.

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?

The description conveys useful context: it applies to one user action across the stack and explains token-scoped visibility. However, it never states when to prefer this tool over sibling tools or when not to use it, so the usage guidance remains implied rather than 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