Skip to main content
Glama
Sign In

Invoke Human Tool

by com.invokehumantool
OverviewDiscussionsAdmin

Import an image from a URL

import_image_url

Fetch one public https URL and store it like upload_image. Private, link-local, and loopback addresses are blocked. Redirects are followed only when the next host is also public https. The type is sniffed and the file must be 2 MB or smaller. Returns image_id, mime, bytes, and sha256. 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": {
      "url": "<url>"
    },
    "name": "import_image_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
altNoShort description stored with the image. At most 200 characters.
urlYesPublic https URL. Port 443 only. No credentials.

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 already declare openWorldHint=true, readOnlyHint=false, idempotentHint=false, and destructiveHint=false. The description adds substantial operational context beyond annotations, including SSRF-style network restrictions, redirect policy, MIME sniffing, size limit, return fields, and the fact that it does not send a handoff.

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 compact and front-loaded: it states the core action first, then security/network constraints, size/type rules, return values, and the handoff caveat. Every sentence carries actionable information.

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?

There is no output schema, but the description lists the returned fields. Combined with annotation coverage and complete schema descriptions, the definition gives an agent enough information to invoke the tool correctly and understand its boundaries.

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 schema documents both parameters thoroughly. The description adds useful semantics for the url parameter beyond the schema, particularly redirect handling, private-address blocking, type sniffing, and the 2 MB limit, while alt is left entirely to the 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 states a specific verb and resource: fetch one public https URL and store it like upload_image. It clearly distinguishes this tool from upload_image by focusing on URL import rather than direct upload, and from the handoff siblings by noting it does not send a handoff.

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?

It gives clear applicability constraints: public https only, private/link-local/loopback blocked, redirects restricted to public https, type sniffing, and a 2 MB size limit. It references upload_image as a comparable storage path but does not explicitly say when to choose this tool over upload_image beyond the URL-based input.

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