Tasvr

Browse the preset catalog as a tree

browse_presets

Read-only

Opens the preset catalogue one level at a time as a tree. A row's id is the path of its next level; a leaf row carries a preset id.

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

Input Schema

Name	Required	Description
`path`	No	A node id from a previous call, e.g. "environment/locations/Kerala". Omit for the root.
`limit`	No	Items per page (max 100).
`cursor`	No	The nextCursor from the previous page.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description discloses critical behavioral logic that extends beyond the schema and annotations, detailing that row IDs function as paths for lower levels, and only leaf rows contain actual preset IDs. This explains the recursive nature of the data structure.

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 definition is highly concise, using two direct sentences to explain the core functionality and the structure of the navigation mechanics. There is no redundant or superfluous language.

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?

Given that the schema handles pagination (limit/cursor), the description fully completes the user's understanding of the tool's operational logic: it describes how one moves through the hierarchy (level by level, leaf vs. branch node).

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?

The description provides vital semantic context for the 'path' parameter, clarifying that it holds a node ID from a previous call and explains the significance of a 'leaf row,' which adds high value beyond the 100% schema coverage.

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 excels at defining the mechanism of the tool, specifying that it navigates the 'preset catalogue... as a tree.' This clear, highly specialized functionality is the key differentiator from other listing tools in the sibling set.

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

Usage Guidelines4/5

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

While it does not explicitly name alternative tools (like list_presets), it defines the tool's specific hierarchical nature, clearly signaling that it should be used for exploratory, depth-first catalog navigation rather than flat searching or bulk listing.

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?