Skip to main content
Glama

The Doll Scout Home Tools

Compare two all-in quotes · Photography space quotes

tds_quote_photo_studio
Read-onlyIdempotent

Add each recurring cost over your chosen comparison period to the one-time quote. Photography space quotes. Months of photo workspace use.

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": {
      "offerAUpfrontCents": "<offerAUpfrontCents>",
      "offerBUpfrontCents": "<offerBUpfrontCents>",
      "offerAMonthlyCents": "<offerAMonthlyCents>",
      "offerBMonthlyCents": "<offerBMonthlyCents>",
      "photoStudioMonths": "<photoStudioMonths>"
    },
    "name": "tds_quote_photo_studio"
  }
}

Input Schema

NameRequiredDescriptionDefault
photoStudioMonthsYes
offerAMonthlyCentsYes
offerAUpfrontCentsYes
offerBMonthlyCentsYes
offerBUpfrontCentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one useful behavioral fact beyond that: the result is a combination of monthly costs multiplied across the chosen period plus a one-time amount. It says nothing about what the response contains or whether both offers are compared side by side.

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 core sentence is short and front-loaded, but the two following sentence fragments add no operational information and dilute the definition. Roughly half the text does not earn its place.

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

Completeness3/5

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

With five required, undocumented parameters and no output schema, the definition should explain the A/B comparison structure and the return shape. It explains the arithmetic relationship adequately but leaves the agent guessing how offer A and offer B results are presented and in what units inputs are expected.

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 must carry the semantics. It only partially does: it implies that monthly figures are recurring and multiplied by the period and that upfront figures are one-time, but it never mentions the A/B offer pairing explicitly, never states units (cents), and never clarifies the 1–120 month bound.

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 conveys a computation (recurring cost over a period added to a one-time quote) but never states the actual job in a single clear clause: compare two all-in photography-studio quotes. The two trailing fragments ('Photography space quotes. Months of photo workspace use.') read as keyword padding rather than a purpose statement, and nothing distinguishes it from siblings like tds_quote_storage_space.

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 mention of when to pick this over the many other tds_quote_* tools, and no prerequisites or exclusions. The agent must infer entirely from the name that this is the tool for comparing two photography-space offers.

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.