Skip to main content
Glama
skr-electronics-lab

Agent Cam MCP Tool

by skr-electronics-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_camera_settings

Adjust hardware camera parameters such as exposure, focus, brightness, contrast, gain, and white balance, or lock auto settings. Reports which values the driver accepted or rejected.

Instructions

Adjust hardware camera parameters: exposure, focus, brightness, contrast, gain, white balance, or lock auto settings. Reports exactly which parameters were accepted vs rejected by the driver.

Input Schema

NameRequiredDescriptionDefault
gainNoGain value
focusNoManual focus value
cameraYesCamera ID
contrastNoContrast value
exposureNoManual exposure value
lock_autoNoLock auto-exposure/focus to current values
brightnessNoBrightness value
white_balanceNoWhite balance value

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / contrast
      Added value: +{
+  "description": "Contrast value",
+  "type": "integer"
+}
    • addedInput schema / properties / gain
      Added value: +{
+  "description": "Gain value",
+  "type": "integer"
+}
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose one genuinely valuable behavioral trait beyond the schema: partial-failure semantics, i.e. the driver may accept some parameters and reject others, and the result reports which. It omits persistence (do settings survive across sessions?), permission requirements, and whether changing exposure affects other parameters.

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?

Two tight sentences with zero waste: the capability and its parameter set come first, and the notable return behavior follows. Nothing is padded or restated from the schema.

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

Completeness3/5

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

For an 8-parameter hardware mutation with no annotations and no output schema, the definition is only partially complete. The accepted-vs-rejected reporting usefully substitutes for an output schema, but the lack of any range/unit context for hardware values and the absence of any failure or permission caveats leave real gaps.

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 every parameter is already documented in the schema; the description merely re-lists the same names. No units, ranges, or interaction rules (e.g. valid range for gain or exposure) are added beyond the structured fields. Baseline 3 applies when the schema does the heavy lifting.

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 (Adjust) plus the resource (hardware camera parameters) and enumerates exactly which knobs are in scope, including the 'lock auto settings' mode. No sibling tool touches camera hardware configuration, so an agent can route to this unambiguously.

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?

Usage is implied by the enumeration of adjustable parameters and the lock_auto mode, and there is no competing sibling to steer away from. However, there is no explicit when-to-use statement, no prerequisite (e.g. camera must be open/idle), and no guidance on whether to lock auto first or set values first.

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

Deploy Server

Other Tools