smartscale

scale_objects_from_credit_card

Scale object pixel dimensions using a standard CR80 credit card reference.

Args:
    image_id: Caller-defined source identifier; no image is uploaded.
    credit_card_pixel_width: Caller-supplied pixel width of a CR80-size card.
    objects: Objects to scale. Each object needs pixel_width and pixel_height;
        label, pixel_area, pixel_perimeter, and input confidence are optional.
    credit_card_pixel_height: Optional caller-supplied height for distortion check.
    payment_ref: Optional paid escrow reference consumed by the gateway.
    request_id: Optional retry-safe idempotency key (maximum 128 characters).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`objects`	Yes
`image_id`	Yes
`request_id`	No
`payment_ref`	No
`credit_card_pixel_width`	Yes
`credit_card_pixel_height`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`error`	No
`field`	No
`result`	No
`status`	Yes
`message`	No
`timestamp`	No
`constraint`	No
`error_type`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed14 schema fields changedJul 27, 2026

addedInput schema / properties / payment_ref

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Payment Ref"
+}

addedInput schema / properties / request_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Request Id"
+}

addedOutput schema / properties / constraint

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Constraint"
+}

addedOutput schema / properties / data

Added value: +{
+  "default": null,
+  "title": "Data"
+}

addedOutput schema / properties / error

Added value: +{
+  "default": null,
+  "title": "Error"
+}

addedOutput schema / properties / error_type

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Error Type"
+}

addedOutput schema / properties / field

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Field"
+}

addedOutput schema / properties / message

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Message"
+}

addedOutput schema / properties / result / default
```
Added value: +null
```
removedOutput schema / properties / result / type
```
Removed value: -"string"
```

addedOutput schema / properties / status

Added value: +{
+  "title": "Status",
+  "type": "string"
+}

addedOutput schema / properties / timestamp

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Timestamp"
+}

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "status"
+]

changedOutput schema / title

Previous value: -"scale_objects_from_credit_cardOutput"New value: +"FleetToolResult"

First observedJul 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The description reveals key behaviors: no image upload, caller-supplied dimensions, optional distortion check, payment ref consumed by gateway, and idempotency key. With no annotations, this provides adequate behavioral context, though it does not mention error handling or side effects.

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

Conciseness4/5

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

The description is front-loaded with a one-sentence summary followed by a structured Args section. It is informative without being overly verbose, though the Args list could be slightly trimmed without losing clarity.

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

Completeness5/5

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

Given the tool's complexity (6 parameters, 3 required) and the existence of an output schema, the description covers all necessary aspects: parameter explanations, domain-specific details (CR80, distortion check), and optional fields. It is complete for an AI agent to use correctly.

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

Parameters5/5

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

With schema description coverage at 0%, the description fully explains each parameter: image_id is a source identifier, credit_card_pixel_width is the card's pixel width, objects need pixel_width/height, etc. This adds significant meaning beyond the raw schema.

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

Purpose5/5

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

The description clearly states the tool's action ('Scale object pixel dimensions') and the reference method ('CR80 credit card'). It is specific and distinct from sibling tools, which are about instructions, description, and health.

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 explicit guidance on when to use this tool versus alternatives (e.g., if a different scaling method is needed). The description lacks when-not-to-use or context for choosing this over sibling tools.

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

All smartscale tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: instructions for photo capture, description of capabilities, health check, and object scaling. No overlap or ambiguity.

Naming Consistency5/5

All tool names use consistent snake_case pattern. While some are multi-word and others single-word, they follow the same convention without mixing styles.

Tool Count5/5

With only 4 tools, the server is well-scoped for its purpose of providing credit card-based measurement. Each tool is essential and there are no superfluous ones.

Completeness4/5

The server covers the core workflow: instructions, scaling, health, and capabilities. It lacks a tool for uploading images or retrieving historical results, but these may be handled externally.

scale_objects_from_credit_card

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources