Skip to main content
Glama

The Doll Scout Home Tools

Check remaining purchase budget · Art framing budget

tds_budget_art_frame
Read-onlyIdempotent

Reserve the named cost, subtract commitments, then calculate whole affordable units. Art framing budget. Reserve for mats and backings (cents).

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": {
      "budgetCents": "<budgetCents>",
      "committedCents": "<committedCents>",
      "costPerUnitCents": "<costPerUnitCents>",
      "artMatReserveCents": "<artMatReserveCents>"
    },
    "name": "tds_budget_art_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
budgetCentsYes
committedCentsYes
costPerUnitCentsYes
artMatReserveCentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description's 'Reserve the named cost' language is genuinely ambiguous against a read-only hint — it is unclear whether a reservation is persisted or merely an arithmetic step — and nothing is said about rounding, floor behavior, or what happens when commitments exceed budget.

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?

Three short sentences with no filler, but the structure is poor: the most cryptic clause ('Reserve the named cost') is front-loaded and the standalone fragment 'Art framing budget' merely repeats the title rather than adding information.

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?

There is no output schema, so the description is the only place the return value can be explained — yet it never states whether the result is a unit count, a remaining-balance, or both, nor whether the mat reserve is deducted before dividing. For a four-required-parameter computation tool with zero schema coverage, that is a substantial gap.

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 0%, so the description must carry parameter meaning, and it partially does: 'commitments' maps to committedCents, 'cost per unit' to costPerUnitCents, and 'mats and backings (cents)' to artMatReserveCents. However budgetCents is never explicitly addressed and the relationship (what is subtracted from what, and where the reserve enters) remains unclear.

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 phrase 'calculate whole affordable units' combined with the title 'Art framing budget' conveys that this is a budget-to-units computation. But the opening clause 'Reserve the named cost' is opaque — the cost is not named anywhere — and the description does nothing to distinguish this from the many sibling tds_budget_* tools beyond the label 'Art framing budget'.

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?

No when-to-use or when-not-to-use guidance is given, and no alternatives among the ~20 sibling tds_budget_* tools are named. An agent must infer from the title alone that this applies to framing/matting purchases rather than binder covers, sleeves, or staging.

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.