Skip to main content
Glama

The Doll Scout Home Tools

Compare measured shelf load · Items in a drawer insert

tds_drawer_organizer_mass
Read-onlyIdempotent

Sum the item mass, supports and named extra load against a rating supplied by the user. Items in a drawer insert. Mass of the insert’s containers (g).

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": {
      "itemCount": "<itemCount>",
      "massPerItemG": "<massPerItemG>",
      "standMassG": "<standMassG>",
      "ratingG": "<ratingG>",
      "containerMassG": "<containerMassG>"
    },
    "name": "tds_drawer_organizer_mass"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratingGYes
itemCountYes
standMassGYes
massPerItemGYes
containerMassGYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare this as a read-only, idempotent, closed-world, non-destructive operation, so the safety profile needs no restating. The description usefully adds that the rating is user-supplied rather than looked up, but with no output schema it should also say what the result looks like (a pass/fail verdict, a margin in grams, or the summed total) and it does not.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short with no padding, but the structure is poor: three sentence fragments of differing register (an instruction, a domain note, a unit note) are stacked without connective logic, so the reader must reconstruct the intent.

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

Completeness2/5

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

Five required parameters at 0% schema coverage and no output schema demand a fuller definition than this. An agent can guess the arithmetic but cannot confirm how itemCount combines with massPerItemG, what happens to 'named extra load', or what the tool returns, which is insufficient for a computation tool of this complexity.

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

Parameters2/5

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

Schema description coverage is 0% across five required parameters, so the description carries the full burden. It loosely maps 'item mass' to massPerItemG, 'supports' to standMassG, 'rating supplied by the user' to ratingG, and 'Mass of the insert's containers (g)' to containerMassG, but it never explains itemCount, never clarifies that item mass is per-item times count, and its phrase 'named extra load' corresponds to no parameter in the schema, leaving genuine ambiguity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description does convey a computation ('Sum the item mass, supports and named extra load against a rating'), which is more than a restatement of the name, but the purpose is delivered in three disconnected fragments. It never states plainly that this is a drawer-organizer load check returning a comparison to a rating, and it draws no boundary against load-calculation siblings such as tds_tote_loading_mass or tds_art_print_table_load.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of any alternative tool for related load or capacity checks. The only contextual hint is 'Items in a drawer insert', which identifies a domain but not a selection rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.