Return SmartScale capabilities and input contract.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | ||
| error | No | ||
| field | No | ||
| result | No | ||
| status | Yes | ||
| message | No | ||
| timestamp | No | ||
| constraint | No | ||
| error_type | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Output schema / properties / constraintAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "title": "Constraint"
+}Output schema / properties / dataAdded value: +{
+ "default": null,
+ "title": "Data"
+}Output schema / properties / errorAdded value: +{
+ "default": null,
+ "title": "Error"
+}Output schema / properties / error_typeAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "title": "Error Type"
+}Output schema / properties / fieldAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "title": "Field"
+}Output schema / properties / messageAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "title": "Message"
+}Output schema / properties / result / defaultAdded value: +nullOutput schema / properties / result / typeRemoved value: -"string"Output schema / properties / statusAdded value: +{
+ "title": "Status",
+ "type": "string"
+}Output schema / properties / timestampAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "title": "Timestamp"
+}Output schema / requiredPrevious value: -[
- "result"
-]New value: +[
+ "status"
+]Output schema / titlePrevious value: -"describeOutput"New value: +"FleetToolResult"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must convey behavioral traits. 'Return' implies a read-only operation, but no details about side effects or requirements are given. The simplicity of the tool (0 params) partially justifies the minimal description, but it could be more explicit.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that directly states the tool's purpose with no unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has no parameters and an output schema, the description is nearly complete. It clearly states what is returned, but could briefly mention that it is a read-only introspection tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has zero parameters, so the baseline is 4. The description adds no parameter details, but none are needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns 'SmartScale capabilities and input contract', using a specific verb and resource. It distinguishes from sibling tools like `credit_card_photo_instructions` and `scale_objects_from_credit_card`, which have different purposes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It lacks context such as prerequisites or typical use cases, which is particularly needed given the sibling tools exist.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: instructions for photo capture, description of capabilities, health check, and object scaling. No overlap or ambiguity.
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.
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.
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.