Skip to main content
Glama

The Doll Scout Home Tools

Check remaining purchase budget · Photo accessories

tds_budget_photography_accessories
Read-onlyIdempotent

Reserve the named cost, subtract commitments, then calculate whole affordable units. Photo accessories. Light stand reserve (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>",
      "lightSupportReserveCents": "<lightSupportReserveCents>"
    },
    "name": "tds_budget_photography_accessories"
  }
}

Input Schema

NameRequiredDescriptionDefault
budgetCentsYes
committedCentsYes
costPerUnitCentsYes
lightSupportReserveCentsYes

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 establish that this is a safe, read-only, idempotent, non-destructive, closed-world calculation. The description adds some behavioral context by outlining a reserve-subtract-calculate sequence and stating that the result is in whole units. It does not fully clarify rounding, whether the reserve is separate from commitments, or what the calculation does when funds are insufficient.

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?

The description is short and front-loads the calculation sequence, so it is not bloated. However, the fragment 'Photo accessories. Light stand reserve (cents).' is choppy and leaves important connections implicit. The brevity reflects under-specification rather than efficient communication.

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?

This is a four-parameter calculation tool with no schema descriptions and no output schema, so the description needs to explain both the input formula and the expected result. It mentions whole affordable units but does not define the return value, rounding behavior, or how all inputs combine. For a budget tool with no other documentation, this is incomplete.

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%, so the description must compensate for all four required parameters. It only hints at the light stand reserve via 'Light stand reserve (cents)' and loosely gestures at commitments and cost per unit, without mapping them to budgetCents, committedCents, or costPerUnitCents. This leaves the parameter meanings substantially under-specified.

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 implies a budget calculation that reserves a light stand cost, subtracts commitments, and returns affordable whole units for photo accessories. However, the opening phrase 'Reserve the named cost' is vague and the purpose is not stated as cleanly as the title's 'Check remaining purchase budget'. It gives enough signal to guess the tool's function but not a precise verb-and-resource statement.

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 guidance on when to use this tool, when not to use it, or which sibling budget tools are alternatives. The description does not mention prerequisites, applicable scenarios, or exclusions. The agent must infer usage entirely from the name and title.

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.