Skip to main content
Glama

smartscale

by io.github.jdhart81
OverviewDiscussionsAdmin

credit_card_photo_instructions

Return safe capture guidance for upstream CR80 pixel picking.

The image stays with the caller or upstream vision system; SmartScale only receives numeric pixel geometry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
measurement_goalNo
objects_to_measureNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
errorNo
fieldNo
resultNo
statusYes
messageNo
timestampNo
constraintNo
error_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • 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: -"credit_card_photo_instructionsOutput"New value: +"FleetToolResult"
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

The description discloses that the image is not sent to SmartScale, only numeric pixel geometry is received, which is key behavioral info. However, with no annotations, additional details like idempotency or side effects are missing.

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

Conciseness5/5

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

The description is extremely concise with two sentences, no fluff, and the key purpose is front-loaded.

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?

While the output schema exists, the description fails to contextualize the two input parameters, which are crucial for the agent to use the tool correctly. The overall guidance is incomplete for a tool with undocumented parameters.

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

Parameters1/5

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

The description does not explain the parameters 'measurement_goal' and 'objects_to_measure' at all, leaving their purpose and values ambiguous. With 0% schema description coverage, this is a significant gap.

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

Purpose4/5

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

The description clearly states the tool returns safe capture guidance for CR80 pixel picking, which is a specific action and distinguishes it from siblings like 'scale_objects_from_credit_card' which processes images. However, the term 'CR80 pixel picking' may be too technical and not immediately clear.

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?

The description does not provide any explicit guidance on when to use this tool versus alternatives. It implies usage for obtaining capture guidance but fails to mention prerequisites or when not to use it.

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

All smartscale toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources