Skip to main content
Glama
Sign In

Invoke Human Tool

by com.invokehumantool
OverviewDiscussionsAdmin

Upload an image

upload_image
Idempotent

Store a PNG, JPEG, or WebP on this account and return its img_ id. Pass data_base64. alt is optional. The type is sniffed from the bytes, not the name. The limit is 2 MB. The same bytes on this account return the same image_id. Reference that id on an image or gallery block, or as alt. An https or data URL is rejected. This does not send a handoff.

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

Input Schema

NameRequiredDescriptionDefault
altNoShort description stored with the image. At most 200 characters.
data_base64YesBase64-encoded PNG, JPEG, or WebP. At most 2 MB decoded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations cover the safety profile, and the description adds real behavioral context beyond them: content-type is sniffed from bytes not filename, a 2 MB cap applies, identical bytes return the identical image_id (concretizing idempotentHint), and it explicitly 'does not send a handoff,' defusing confusion with the handoff siblings.

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?

Short declarative fragments, front-loaded with what it does and returns before constraints and usage. No filler sentences; each clause carries a distinct constraint or downstream reference.

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?

Even without an output schema, the description gives the return shape (img_ id), the error condition (URLs rejected), the size limit, dedup semantics, and how to consume the id in blocks or markdown. Nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the 3-baseline applies, but the description adds that there is no format/filename parameter because the type is sniffed from the bytes. That is meaningful guidance the schema cannot express, nudging the score up.

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?

States a specific verb and resource ('Store a PNG, JPEG, or WebP on this account') plus the return value ('return its img_ id'). The URL-rejection clause implicitly separates it from import_image_url, so the agent can pick correctly without reading both schemas.

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?

Tells the agent what to pass ('Pass data_base64'), that alt is optional, and that URL inputs are rejected. It stops short of naming import_image_url as the alternative for http/data URLs, leaving that one hop to inference.

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

All Invoke Human Tool 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