Skip to main content
Glama
capad-xyz

searchts

by capad-xyz
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Local

fetch_asset

Download a single asset file from its URL, bypassing common bot walls, save to disk, and return path, content type, and byte count as JSON.

Instructions

Download a single asset file (image, PDF, font, CSS, any file) from its URL through the same unlock ladder as read_url, save it to disk, and return {path, content_type, bytes} as JSON. Use this for one specific file by its direct URL; to pull a whole page's assets at once use grab_site instead. Saves into out_dir when given, otherwise the current directory. Returns an 'Error: ...' string on failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
out_dirNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.8.0
    • addedInput schema / properties / out_dir / default
      Added value: +""
    • removedInput schema / properties / out_dir / description
      Removed value: -"Directory to save into (optional; defaults to the current directory)."
    • addedInput schema / properties / out_dir / title
      Added value: +"Out Dir"
    • removedInput schema / properties / url / description
      Removed value: -"Direct URL of the asset file to download."
    • addedInput schema / properties / url / title
      Added value: +"Url"
    • addedInput schema / title
      Added value: +"fetch_asset_toolArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "fetch_asset_toolOutput",
+  "type": "object"
+}
  2. First observedv0.5.1

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It discloses that the tool saves to disk, respects out_dir with a default fallback, returns {path, content_type, bytes} as JSON, and returns an Error string on failure. It does not explain the 'unlock ladder' mechanism in detail, but the reference to read_url provides enough context.

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 three tightly packed sentences with no filler. The core action and return shape come first, usage guidance follows, and failure behavior ends the description. Every sentence earns its place.

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 two-parameter tool with an output schema, this description provides enough context to select and invoke the tool correctly: what it downloads, where it saves, what it returns, and how it differs from grab_site. The only mild gap is that 'same unlock ladder as read_url' presumes familiarity with read_url's behavior, but siblings are available for that context.

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 0%, so the description must compensate. It explains url as a direct URL to one asset file and out_dir as the save destination with current-directory fallback. It does not specify filename derivation or accepted URL schemes, but it adds meaning beyond the bare parameter names.

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 names a specific action (download), a specific resource (a single asset file by direct URL), and the concrete outcomes (save to disk, return JSON). It also distinguishes itself from grab_site by explicitly stating it is for one file rather than a whole page's assets.

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?

The description explicitly says when to use this tool ('for one specific file by its direct URL') and names the alternative for the opposite case ('to pull a whole page's assets at once use grab_site instead'). This gives an agent clear routing guidance without requiring schema inspection.

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

Install Server

Other Tools