Skip to main content
Glama
juanucilla

travaso

by juanucilla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local
README.md
Hózhǫ́ǫ́go naasháa doo,  
tʼáá íídą́ą́ʼ shił bééhózin — hózhǫ́ǫ́go.  
Tʼáá ałtso náhásdlį́į́ʼ,  
hózhǫ́ náhásdlį́į́ʼ.
Deploy Server
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

TDQS

A3.5/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: checking state, searching for facts, sequential delivery, absorbing, archive search, and restore. No two tools overlap in function.

Naming Consistency5/5

All tools share the consistent 'travaso_' prefix followed by a clear verb or noun (stato, cerca, prossimi, assorbi, archivio, ripristina). The pattern is uniform and predictable.

Tool Count5/5

Six tools is well within the ideal 3-15 range and each tool serves a necessary step in the transfer workflow without redundancy.

Completeness5/5

The tool set covers the full lifecycle of the transfer process: status check, search-based retrieval, sequential delivery, absorption confirmation, archive lookup, and restore. No obvious gaps in the workflow.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources