Skip to main content
Glama
Sign In

Angelcam

by com.angelcam
OverviewDiscussionsAdmin

Get Camera Broadcasting Status

get_camera_broadcasting
Read-onlyIdempotent

Report whether a camera is publicly broadcast: whether broadcasting is enabled and whether it has a public page. Only cameras with the Broadcasting service have this; others report that it is not active. Stream URLs are not included.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "camera_id": "<camera_id>",
      "session_id": "<session_id>"
    },
    "name": "get_camera_broadcasting"
  }
}

Input Schema

NameRequiredDescriptionDefault
space_idNoAngelcam space. Call list_spaces; if there is more than one, ask the user which and pass its id - never guess or assume the active one. Reuse it on every later call; omit only with a single space.
camera_idYes
session_idYesSession continuity handle, one of two values: the ses_ ID issued for the task underway, or start. This server cannot link your calls between requests on its own, so session continuity travels in this parameter instead. If you were handed a session_id for this task — for example by the agent that spawned you — send that exact value from your first call. Otherwise send start on your first call; the server will issue an opaque correlation ID in the mcp_session field of the result, or in a text block at the start of the result beginning [session_id issued. Then send that exact ses_ value on every later call and hand it to any subagents working the same task. start always begins a new, unrelated task — never send it mid-task. If you send a value this server does not recognize, the result reports it: mcp_session.status of unrecognized, or a text block beginning [session_id unrecognized; re-send the ID issued for this task, or start if none was issued yet. Never invent a ses_ value.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's added value is in disclosing service gating and what the response does and does not contain. That is useful behavioral context beyond the annotations, though it says nothing about behavior for a camera lacking the service beyond 'not active' or about error cases for invalid IDs.

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, front-loaded with the core purpose and finishing with the exclusion constraint. Every clause carries information; nothing is restated from the title or annotations.

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 three-parameter read-only tool with no output schema, the description covers purpose, applicability, and the shape of the result (two booleans, no URLs). It could say more about what happens when the camera isn't broadcasting-capable or when camera_id is invalid, but nothing essential for correct invocation is missing.

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 67%: session_id and space_id are extensively documented in the schema, while camera_id carries no description. The description adds no parameter-level meaning at all, so it neither compensates for the undocumented camera_id nor reinforces the space/session usage rules. Baseline 3 for mostly schema-covered parameters is appropriate.

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 opens with a specific verb and resource ('Report whether a camera is publicly broadcast') and immediately names the two concrete sub-results (broadcasting enabled, public page). The closing clause 'Stream URLs are not included' explicitly separates it from the stream-URL siblings such as get_live_stream_url and get_recording_stream_url.

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 applicability condition: only cameras with the Broadcasting service have this state, and others report it as not active. It also implies the alternative for URL retrieval by excluding stream URLs, but it never names that alternative tool outright, leaving the agent to infer the routing.

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

All Angelcam 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