Skip to main content
Glama
Sign In
sommus-laptop

sommus-laptop

by Jashan-Mshadow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_brightness

Adjust your laptop's built-in display brightness from 0 (darkest) to 100 (brightest). External monitors are not supported.

Instructions

Set the built-in display's brightness (external monitors aren't supported).

Args:
    level: Brightness from 0 (darkest) to 100 (brightest).

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": {
      "level": "<level>"
    },
    "name": "set_brightness"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare this is a write operation that is not destructive (readOnlyHint=false, destructiveHint=false), so the safety profile is covered. The description adds real behavioral context by restricting the hardware scope to the built-in display, but says nothing about persistence, reversibility, or permission requirements.

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?

One scope sentence followed by a single argument line; everything is front-loaded and nothing is padded. The Args block is slightly redundant with the schema but stays within one line.

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 single-parameter setter with no output schema and annotations covering the safety profile, the description supplies the two things an agent needs most: hardware scope and the valid value range. Only persistence/reversibility behavior is unaddressed.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry the parameter, and it does: 'level' is documented as an integer from 0 (darkest) to 100 (brightest), giving both range and direction. Only the unit (percent) is left implicit, which is a minor gap.

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?

Specific verb (Set) plus specific resource (the built-in display's brightness), with an explicit scope boundary that rules out external monitors. An agent can immediately distinguish it from the sibling get_brightness, which reads rather than writes.

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 provides one exclusion — external monitors aren't supported — which is genuine when-not guidance, but it never states when to prefer this tool or what an agent should do instead for external displays. Usage is implied rather than fully specified.

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