Skip to main content
Glama
Sign In
Touchpoint

Touchpoint

by Touchpoint-Labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_numeric_value

Set the numeric value of a range element (slider, spinbox) by specifying the element ID and the target number.

Instructions

Set the numeric value of a range element (slider, spinbox).

Args:
    element_id: The element ID (a slider, spin button, etc.).
    value: The numeric value to set.

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": {
      "element_id": "<element_id>",
      "value": "<value>"
    },
    "name": "set_numeric_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
element_idYes
valueYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states the action without discussing error handling, value constraints, or whether the operation is destructive. Minimal behavioral disclosure.

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?

The description is extremely concise with three short sentences, front-loading the purpose and listing parameters efficiently. No wasted words.

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 simple setter tool with 2 required parameters and an output schema (though not described), the description covers the essentials. It could mention return values or success behavior, but the complexity is low.

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 coverage is 0%, so description adds value by clarifying that element_id is for a range element and value is a numeric. However, it does not provide additional details like accepted range or formatting, so meaning is limited.

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 explicitly states the tool sets a numeric value on range elements (slider, spinbox), which clearly distinguishes it from sibling tools like 'set_value' that handle text input.

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?

The description implies usage for range elements by specifying 'slider, spinbox', giving context on when to use it. However, it does not explicitly state when not to use it or mention alternatives like 'set_value'.

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