Skip to main content
Glama
Sign In
tensorart-mcp

tensorart-mcp

by giacomodiguida
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

upload_image

Upload a local image to TAMS and returns its resource ID for use in workflows or img2img generation.

Instructions

Upload a local image to TAMS and return its resource id (for workflows or img2img).

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": {
      "image_path": "<image_path>"
    },
    "name": "upload_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
image_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the operation uploads a local image and returns a resource id, but it does not mention authentication, supported formats, size limits, overwrite behavior, or error handling for an upload operation.

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 a single, front-loaded sentence with no wasted wording. It states the action, target, return value, and use context efficiently.

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?

For a simple one-parameter upload tool, the description covers the action and return value, and no output schema exists to explain returns. However, it leaves the image_path format and upload constraints unstated, which matters because the schema provides no parameter descriptions and no annotations exist.

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 coverage is 0%, so the description must compensate for the undocumented image_path parameter. It only implies that image_path refers to a local image; it does not clarify whether the path must be absolute or relative, which formats are accepted, or any size constraints.

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 uses a specific verb and resource: "Upload a local image to TAMS." It also states the return value (resource id) and use context (workflows or img2img), distinguishing it from generation tools such as generate_image.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical "for workflows or img2img" gives a clear use context for when an agent would need a resource id. It does not explicitly state when not to use this tool or name an alternative sibling, so it falls short of full when/when-not guidance.

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

Deploy Server

Other Tools