Angelcam

List Cameras With Defect Detection

list_defect_detection_cameras

Read-onlyIdempotent

List the cameras in the space that have defect detection configured. Use it before reading checks: list_defect_detection_checks returns nothing both for a camera that is healthy and for one that was never set up, and this is what tells the two apart. Administrators of the space only.

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": {
      "session_id": "<session_id>"
    },
    "name": "list_defect_detection_cameras"
  }
}

Input Schema

Name	Required	Description	Default
`space_id`	No	Angelcam 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.
`session_id`	Yes	Session 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.

First observedNov 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description's job is to add context — and it does, disclosing the administrator-only authorization requirement and the interpretive caveat about how to read related check results. It stops short of describing the shape of the returned camera entries (identifiers, settings fields) or ordering, which is the remaining behavioral gap.

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 purpose, then the sequencing rationale, then the access constraint. Every sentence carries distinct information and none restates the name or the schema.

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 two-parameter read-only listing tool with a fully documented schema and explicit safety annotations, the description covers purpose, ordering relative to siblings, and access requirements — enough for correct invocation. The one omission is what each returned camera entry contains, which matters more here because no output schema exists.

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% and both parameters (space_id, session_id) are documented thoroughly in the schema, including the 'never guess the active space' rule and session-continuity protocol. The description adds nothing about either parameter, so the baseline of 3 applies.

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?

States a specific verb and resource with a clear filter: 'List the cameras in the space that have defect detection configured.' That filter alone separates it from list_cameras (all cameras) and from list_defect_detection_checks, and the second sentence reinforces the distinction.

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?

Gives explicit sequencing guidance ('Use it before reading checks') together with the reason, and names the sibling tool whose ambiguous empty result this tool disambiguates. It also states the access precondition 'Administrators of the space only,' so an agent knows both when to call it and whether the caller qualifies.

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

All Angelcam tools Inspect

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

Need Help?