list_scalesList registered scales for the account. The id on each row is the number this account knows that record by, counting from 1: safe to show, and what other tools expect back.
| Name | Required | Description | Default |
|---|---|---|---|
| status | No | Filter by status: current (unarchived), archived, or all. Defaults to current. |
| Name | Required | Description | Default |
|---|---|---|---|
| scales | Yes |
Changes observed during successful MCP inspections.
Output schema / properties / scales / items / properties / auto_tare / typeRemoved value: -"null"Output schema / properties / scales / items / properties / auto_timer / typeRemoved value: -"null"Output schema / properties / scales / items / properties / capacity_g / typeRemoved value: -"null"Output schema / properties / scales / items / properties / connectivity / typeRemoved value: -"null"Output schema / properties / scales / items / properties / depth_mm / typeRemoved value: -"null"Output schema / properties / scales / items / properties / flow_rate_display / typeRemoved value: -"null"Output schema / properties / scales / items / properties / height_mm / typeRemoved value: -"null"Output schema / properties / scales / items / properties / notes / typeRemoved value: -"null"Output schema / properties / scales / items / properties / power / typeRemoved value: -"null"Output schema / properties / scales / items / properties / water_resistance / typeRemoved value: -"null"Output schema / properties / scales / items / properties / width_mm / typeRemoved value: -"null"Output schema / properties / scales / itemsAdded value: +{
+ "additionalProperties": true,
+ "properties": {
+ "archived": {
+ "type": "integer"
+ },
+ "auto_tare": {
+ "type": "null"
+ },
+ "auto_timer": {
+ "type": "null"
+ },
+ "capacity_g": {
+ "type": "null"
+ },
+ "connectivity": {
+ "type": "null"
+ },
+ "depth_mm": {
+ "type": "null"
+ },
+ "flow_rate_display": {
+ "type": "null"
+ },
+ "height_mm": {
+ "type": "null"
+ },
+ "id": {
+ "type": "integer"
+ },
+ "name": {
+ "type": "string"
+ },
+ "notes": {
+ "type": "null"
+ },
+ "power": {
+ "type": "null"
+ },
+ "resolution_banded": {
+ "type": "integer"
+ },
+ "resolution_g": {
+ "type": "number"
+ },
+ "scale_type": {
+ "type": "string"
+ },
+ "water_resistance": {
+ "type": "null"
+ },
+ "width_mm": {
+ "type": "null"
+ }
+ },
+ "required": [
+ "id",
+ "name",
+ "scale_type",
+ "resolution_g",
+ "resolution_banded",
+ "capacity_g",
+ "width_mm",
+ "depth_mm",
+ "height_mm",
+ "water_resistance",
+ "connectivity",
+ "flow_rate_display",
+ "auto_tare",
+ "auto_timer",
+ "power",
+ "notes",
+ "archived"
+ ],
+ "type": "object"
+}Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "properties": {
+ "scales": {
+ "type": "array"
+ }
+ },
+ "required": [
+ "scales"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the description does not need to restate safety. It adds valuable behavioral context by explaining that the id is a stable, user-facing number counting from 1 and is what other tools expect back.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the purpose and then a useful clarification about the id field. Every sentence contributes without repetition or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple one-parameter schema, rich annotations, and an existing output schema, the description is complete enough for correct invocation. It covers purpose and the non-obvious id semantics without needing to explain return values.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, including a fully documented status enum with default behavior, so the schema carries parameter semantics. The description adds no additional detail about the status parameter, making the baseline 3 appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource ("List registered scales") and scopes it to the account, clearly distinguishing it from register_scale, update_scale, and the other list_* siblings by resource.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It conveys the basic purpose but gives no explicit guidance on when to choose list_scales over alternatives, no prerequisites, and no exclusions. The note about id semantics is useful but does not tell an agent when to invoke the tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.