Tasvr

Keep an uploaded reference image in the human's library

save_reference_to_library

Adds an uploaded reference or an isolated cutout to the account's library, by url or generation id.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	The url or ref upload_reference_image returned, OR an isolate_reference_item result: its isolatedReference url, or the generation_id from get_generation_status.
`label`	No	A short human-readable name, e.g. "Blue serum bottle".

Output Schema

Name	Required	Description	Default
`ref`	No
`url`	Yes
`referenceId`	Yes
`savedToLibrary`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent write scoped to the account (openWorldHint=false), so the safety profile is covered. The description adds only the accepted input forms; it says nothing about what happens when the same url is saved twice (relevant given idempotentHint=false) or what a saved item contains.

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?

A single sentence that front-loads the action, the two item kinds, and the two input forms, with no filler or hedging.

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?

With an output schema present, return values need not be explained, and both parameters are fully described. A brief note on the typical upload-or-isolate-then-save sequence and duplicate behavior would make it complete for a small mutating tool.

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 both url and label are already documented in detail, including the generation_id fallback and the label example. The description's 'by url or generation id' restates schema content rather than adding new meaning, which is the baseline 3 case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('adds ... to the account's library') and names the two accepted input forms (uploaded reference, isolated cutout), which separates it from upload_reference_image and isolate_reference_item. It stops short of naming those siblings explicitly, so the routing hint is implicit.

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

Usage Guidelines3/5

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

Usage is only implied: the tool persists a reference by url or generation id. There is no explicit guidance on prerequisites (that upload_reference_image or isolate_reference_item must run first) or on when not to save, leaving the agent to infer the workflow from the sibling names.

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

All Tasvr tools Inspect

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

Need Help?