Skip to main content
Glama
Sign In

Tulina

by ai.tulina.mcp
OverviewDiscussionsAdmin

web_image

VIEW a public image from its URL (png, jpeg, gif, webp) — e.g. a product photo whose address serper_scrape or web_read returned. The image comes back as image content you can look at, after one text line giving the URL actually served, the format and the size.

Plain HTTP fetch only (free, no scraper, no browser). Same guard as web_read: internal addresses and the project's excluded_url_prefixes are refused, redirects included. Refused, never cut or converted: an image over 3 MB, an SVG, or an answer that is not an image (format read from the bytes, not from the Content-Type) — for a page, use web_read.

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": "web_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesabsolute public URL (http/https) of the image itself.
_orgNoOrg (id) de CET APPEL. `oto_list_orgs()`.
_groupNoÉquipe (id) de CET APPEL, sous son org parente.
_run_idNoOBLIGATOIRE à chaque appel dès `run_start` ou `data_claim_next` : sans lui, l'écriture sur une ligne réservée est refusée. Hérité seulement si le serveur tient un run actif — n'y compte pas.
_projectNoProjet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
_instanceNoInstance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations present, the description carries the full burden and does: plain HTTP fetch with no scraper/browser, SSRF-style guard (internal addresses and excluded_url_prefixes refused, redirects included), and hard refusal rather than truncation of images over 3 MB, SVGs, or non-image responses. It even discloses that format is sniffed from bytes, not Content-Type.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the action and formats, then layers return shape and constraints in short clauses. Dense but every clause carries information; the parenthetical example is slightly decorative but helps routing.

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?

No output schema exists, so the description supplies the return contract: image content plus one text line with the URL actually served, the format, and the size. Combined with the refusal rules and guard behavior, an agent knows exactly what success and failure look like.

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% and the single meaningful parameter `url` is already documented as "absolute public URL (http/https) of the image itself." The description reinforces the public-URL and image-not-page requirement but adds no syntax or format detail beyond the schema, so baseline 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?

Opens with a specific verb and resource ("VIEW a public image from its URL") and enumerates the accepted formats (png, jpeg, gif, webp), which immediately separates it from text-fetching siblings like web_read and serper_scrape.

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?

States the trigger concretely ("a product photo whose address serper_scrape or web_read returned") and gives the explicit exclusion plus the alternative: "for a page, use web_read". Both when-to-use and when-not-to-use are covered.

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

All Tulina 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