Skip to main content
Glama

Datei aus dem Web holen

asset_add_from_url

Holt eine Datei von einer öffentlichen Web-Adresse in den Workspace – ein Bild, das schon irgendwo liegt (generiert, Stock, die alte Website). Nur http(s), nur öffentliche Server, höchstens so gross wie der Plan erlaubt. Für Dateien vom Rechner des Kunden stattdessen upload_link.

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": {
      "website": "<website>",
      "url": "<url>"
    },
    "name": "asset_add_from_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirNoZielordner (Standard: assets/uploads)
urlYesÖffentliche Web-Adresse einer Datei, z. B. «https://example.com/bild.jpg». Sie wird einmal per HTTP GET geladen wie in einem Browser – kein API-Aufruf, keine Zugangsdaten.
nameNoDateiname im Workspace; sonst aus der Adresse
websiteYesKennung oder Name der Website. Reicht der Zugang ueber mehrere Organisationen und gibt es die Kennung mehrfach, «organisation/website» schreiben.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true; the description adds real context beyond them: scheme restriction to http(s), public-server-only requirement, and a plan-dependent size ceiling. It does not say what happens on name collisions or what the tool returns, which keeps it below a 5.

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?

Three short sentences, front-loaded with the action, then the constraints, then the alternative. Every clause carries information; no restating of the title or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter write tool with annotations covering safety and a fully documented schema, the description covers purpose, constraints and the alternative route. The one gap is that, with no output schema, it never indicates what the agent gets back (e.g. the stored asset reference) or how failures are surfaced.

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

Parameters3/5

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

Schema description coverage is 100%, so url, dir, name and website are already documented in detail (including the single HTTP GET with no credentials and the organisation/website disambiguation). The description adds essentially no parameter-level meaning beyond that, so the baseline of 3 applies.

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 concrete verb and resource: fetching a file from a public web address into the workspace, with examples of what such a file is (generated, stock, the old website). It also names the sibling it is not for (upload_link for local files), so an agent can distinguish it from upload_link without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use conditions (file already exists somewhere on the web) and explicit when-not/alternative ("Für Dateien vom Rechner des Kunden stattdessen upload_link"). It also states hard preconditions: only http(s), only public servers, size capped by the plan.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources