Skip to main content
Glama

Session Summary

boosthis_session_summary
Read-only

Per-screen p50/p75/p95 and worst rating, worst screens first, with p99, spike ratio and stdev spread where the server has them. No read credentials: a dashboard pointer, never empty. Read-only. More projects: your_projects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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

A3.7/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description adds valuable behavioral context: it is a 'dashboard pointer, never empty,' meaning it always returns data without requiring read_token. It also conditions some metrics on 'where the server has them,' disclosing potential data gaps. This adds meaningful nuance beyond the annotation.

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 front-loaded with the key metrics in the first sentence, and the remaining sentences are compact. The phrasing 'No read credentials: a dashboard pointer, never empty' is terse but informative, and the pointer to `your_projects` is a useful aside without bloat.

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 lists the expected metrics (p50/p75/p95, worst, p99, spike ratio, stdev) and notes that some may be absent depending on server data, which gives the agent a good sense of the return shape. It does not fully specify the list structure or ordering, but the first sentence covers the essentials for a simple read-only tool.

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 baseline is 3. The description adds minimal parameter-specific meaning; 'No read credentials' suggests read_token may be unnecessary, but it does not clarify when to use project vs install_id. This is adequate but not compensatory beyond schema.

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 states the tool produces per-screen performance percentiles (p50/p75/p95), worst rating, p99, spike ratio, and stdev spread, which is a specific and unique resource among siblings. It does not explicitly differentiate itself from similar tools like boosthis_snapshot or boosthis_trend, but the metric list is distinctive enough to identify its 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?

The description implies usage for retrieving session summary metrics and notes that no read credentials are needed, but it does not explicitly say when to prefer this over alternatives. The reference to `your_projects` hints at an alternative for more projects but does not specify selection criteria, leaving the agent to infer the context.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources