Tasvr

Find example images

find_examples

Read-only

Lists finished images already public on tasvr.ai: title, image link, tags and a brief that recreates each. Spends nothing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_examples"
  }
}

Input Schema

Name	Required	Description
`tag`	No	Exact tag: a use case ("Food and restaurants"), a festival or a state.
`limit`	No	Items per page (max 12).
`query`	No	Words to match, e.g. "diwali", "tiffin", "Kolkata".
`cursor`	No	The nextCursor from the previous page.

Output Schema

Name	Required	Description
`total`	No	How many items exist in all.
`examples`	Yes
`nextCursor`	No	Pass back as `cursor` to get the next page. Absent on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations cover read-only and non-open-world, but the description adds traits they don't: the images are already public and consuming them costs no credits ('Spends nothing'). It also characterizes the payload as a recreatable brief, which tells the agent what value to expect; pagination behavior is left to the schema.

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?

Two short sentences, front-loaded with what is returned and closed with the cost trait. No redundancy and nothing that could be cut without losing information.

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 four-optional-parameter read tool with an output schema and readOnly annotations, this is nearly sufficient: cost, source domain and payload shape are covered. The only meaningful omission is routing guidance versus generation/preview/listing siblings.

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 tag, limit, query and cursor are already documented in structured form. The description adds no extra guidance on parameter interaction, such as how tag and query combine, so the baseline 3 applies.

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 (lists) and resource (finished images already public on tasvr.ai) and even previews the returned fields (title, image link, tags, recreating brief). It doesn't explicitly name how it differs from lookalike siblings such as list_reference_images or show_results, so it stops short of full sibling differentiation.

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: 'Spends nothing' hints this is the zero-cost path when an agent wants free style inspiration rather than calling generate_image or preview_generation. There is no explicit when-to-use/when-not-to-use statement and no alternative tool is named.

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?