Skip to main content
Glama
Sign In

Brix Digital Signage

by com.brixsignage
OverviewDiscussionsAdmin

Check one screen's health

get_screen_status
Read-onlyIdempotent

Explain the state of one screen.

When to use:

  • Why a screen shows what it shows, why it is blank or wrong, when it was down, or what its TV did.

When NOT to use:

  • A screen's settings, tags or assigned content: use get_items kind screens.

  • Many screens: use get_fleet_report. A picture: use capture_screenshot. A fix: use control_screens.

What to know:

  • Reads what the screen already reported and never contacts it, so it answers for offline screens. Needs screen.view.

Parameters:

  • screenId: one scr_… id from list_items kind screens.

  • view: why (the source on screen: deactivated, emergency, takeover, schedule or default); diagnose (likely cause plus a checklist; guided:true marks a TV/input/cable guess, not a reading); outages (each outage with length and cause); tv (TV off, other input, cable lost; Signage Sticks only).

  • days: outages default 30; tv default and max 14. limit: default 50; max 200 for outages, 500 for tv. Both are ignored for why and diagnose.

  • Example: {screenId:"scr_lobby7", view:"outages", days:7}.

Input Schema

NameRequiredDescriptionDefault
daysNoDays to look back.
viewYesWhat to explain.
limitNoMost rows.
screenIdYesScreen id.

Output Schema

NameRequiredDescriptionDefault
guidedNodiagnose: true when the cause is a guess from a checklist, not a reading.
summaryNoOne plain-language sentence answering the view.
screenIdNoThe screen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / days / description
      Previous value: -"outages and tv only: days to look back. outages default 30; tv default and max 14."New value: +"Days to look back."
    • changedInput schema / properties / limit / description
      Previous value: -"outages and tv only: most rows; default 50 (max 200 outages, 500 tv)."New value: +"Most rows."
    • changedInput schema / properties / screenId / description
      Previous value: -"The screen id, from list_items kind screens."New value: +"Screen id."
    • changedInput schema / properties / view / description
      Previous value: -"What to explain: why, diagnose, outages or tv."New value: +"What to explain."
  2. Added

TDQS

A5/5.0
Behavior5/5

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

Annotations already carry readOnlyHint/idempotentHint/destructiveHint/openWorldHint, but the description adds behavior the annotations cannot: it reads previously-reported data and 'never contacts it' so it works for offline screens, and it requires screen.view. These are non-obvious operational facts.

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?

Front-loaded purpose followed by labeled When/NOT/What to know/Parameters sections, ending with a concrete call example. The density is all signal — every bullet conveys a constraint or routing rule.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-param read tool with an output schema present, the description covers purpose, routing, data-source behavior, permissions, per-view parameter semantics, and an example. No agent-relevant gap remains; return shape is delegated to the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, yet the description goes far beyond it: each enum value is defined (why = source on screen; diagnose = cause plus checklist, with the guided:true caveat; outages; tv with a Signage-Sticks-only restriction), and per-view defaults, maxima, and which params are ignored are all given.

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 opening line 'Explain the state of one screen' states a specific verb and resource, and the 'When NOT to use' block explicitly routes to siblings (get_items kind screens, get_fleet_report, capture_screenshot, control_screens). An agent can distinguish this from every nearby tool without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is spelled out in both directions: 'Why a screen shows what it shows, why it is blank or wrong, when it was down, or what its TV did' for when to use, plus four named alternatives each with the condition that selects them.

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

All Brix Digital Signage 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