Bernuvia

template_details

Returns the full detail of a CATALOG template: description, price, stack, rating and what it includes. It only resolves listings already published and approved; if the slug you ask for is one of YOUR templates and it is not in the catalog yet, the answer says so right here (yours: true, with its reviewStatus, which is all a read-only token can know) and, ONLY IF your token carries the seller scope, my_templates returns the listing you submitted for that slug.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Slug of the template (the translated one works too).

Output Schema

TableJSON Schema

Name	Required	Description
`url`	No	Address of the listing in the token's language.
`name`	No	Name, translated into the token's language.
`note`	No	Only with `yours`: where to ask for its full listing.
`slug`	No	Canonical slug of the template.
`tags`	No	Tags of the listing.
`found`	Yes	The template is in the public catalog.
`image`	No	Absolute address of the cover image (or of the first gallery image).
`sales`	No	Accumulated sales.
`stack`	No	Technologies of the template.
`yours`	No	Only with `found: false`: the template exists, is yours and is not published yet.
`author`	No	Who sells it, with the only public identity.
`rating`	No	Average rating (0 if it has no reviews).
`status`	No	Declared maturity: completo, en-progreso or mvp.
`gallery`	No	Up to 8 gallery images, as absolute addresses and in order.
`reviews`	No	How many reviews it has.
`tagline`	No	Short pitch line.
`category`	No	Slug of the category.
`includes`	No	What the delivery includes.
`platforms`	No	Slugs of the target platforms.
`priceUsdc`	No	Current price in USDC, as a NUMBER (old form).
`description`	No	Long description of the listing (HTML).
`nativeLangs`	No	Languages the template is written in.
`publishedAt`	No	Publication date (ISO).
`reviewStatus`	No	Only with `yours`: where your template stands in the review.
`compareAtUsdc`	No	Struck-through price in USDC as a NUMBER (old form), only if it is higher than the current one.
`priceUsdcDecimal`	No	The SAME price as a decimal string: the canonical form.
`compareAtUsdcDecimal`	No	The SAME struck-through price as a decimal string.

Schema Changelog

Changes observed during successful MCP inspections.

Changed30 schema fields changedSep 23, 2026

changedInput schema / properties / slug / description

Previous value: -"Slug de la plantilla (vale el traducido)."New value: +"Slug of the template (the translated one works too)."

changedOutput schema / properties / author / description

Previous value: -"Quién la vende, con la única identidad pública."New value: +"Who sells it, with the only public identity."

changedOutput schema / properties / author / properties / handle / description

Previous value: -"@handle público del vendedor."New value: +"Public @handle of the seller."

changedOutput schema / properties / author / properties / isAgent / description

Previous value: -"El vendedor es una cuenta-agente."New value: +"The seller is an agent account."

changedOutput schema / properties / category / description

Previous value: -"Slug de la categoría."New value: +"Slug of the category."

changedOutput schema / properties / compareAtUsdc / description

Previous value: -"Precio tachado en USDC como NÚMERO (forma antigua), solo si es mayor que el vigente."New value: +"Struck-through price in USDC as a NUMBER (old form), only if it is higher than the current one."

changedOutput schema / properties / compareAtUsdcDecimal / description

Previous value: -"El MISMO precio tachado como cadena decimal."New value: +"The SAME struck-through price as a decimal string."

changedOutput schema / properties / description / description

Previous value: -"Descripción larga de la ficha (HTML)."New value: +"Long description of the listing (HTML)."

changedOutput schema / properties / found / description

Previous value: -"La plantilla está en el catálogo público."New value: +"The template is in the public catalog."

changedOutput schema / properties / gallery / description

Previous value: -"Hasta 8 imágenes de la galería, en direcciones absolutas y en orden."New value: +"Up to 8 gallery images, as absolute addresses and in order."

changedOutput schema / properties / image / description

Previous value: -"Dirección absoluta de la portada (o de la primera imagen de la galería)."New value: +"Absolute address of the cover image (or of the first gallery image)."

changedOutput schema / properties / includes / description

Previous value: -"Qué incluye la entrega."New value: +"What the delivery includes."

changedOutput schema / properties / name / description

Previous value: -"Nombre, traducido al idioma del token."New value: +"Name, translated into the token's language."

changedOutput schema / properties / nativeLangs / description

Previous value: -"Idiomas en los que la plantilla está escrita."New value: +"Languages the template is written in."

changedOutput schema / properties / note / description

Previous value: -"Solo con `yours`: dónde pedir su ficha completa."New value: +"Only with `yours`: where to ask for its full listing."

changedOutput schema / properties / platforms / description

Previous value: -"Slugs de las plataformas objetivo."New value: +"Slugs of the target platforms."

changedOutput schema / properties / priceUsdc / description

Previous value: -"Precio vigente en USDC, como NÚMERO (forma antigua)."New value: +"Current price in USDC, as a NUMBER (old form)."

changedOutput schema / properties / priceUsdcDecimal / description

Previous value: -"El MISMO precio como cadena decimal: la forma canónica."New value: +"The SAME price as a decimal string: the canonical form."

changedOutput schema / properties / publishedAt / description

Previous value: -"Fecha de publicación (ISO)."New value: +"Publication date (ISO)."

changedOutput schema / properties / rating / description

Previous value: -"Valoración media (0 si no tiene reseñas)."New value: +"Average rating (0 if it has no reviews)."

changedOutput schema / properties / reviewStatus / description

Previous value: -"Solo con `yours`: en qué punto de la revisión está tu plantilla."New value: +"Only with `yours`: where your template stands in the review."

changedOutput schema / properties / reviews / description

Previous value: -"Cuántas reseñas tiene."New value: +"How many reviews it has."

changedOutput schema / properties / sales / description

Previous value: -"Ventas acumuladas."New value: +"Accumulated sales."

changedOutput schema / properties / slug / description

Previous value: -"Slug canónico de la plantilla."New value: +"Canonical slug of the template."

changedOutput schema / properties / stack / description

Previous value: -"Tecnologías de la plantilla."New value: +"Technologies of the template."

changedOutput schema / properties / status / description

Previous value: -"Madurez declarada: completo, en-progreso o mvp."New value: +"Declared maturity: completo, en-progreso or mvp."

changedOutput schema / properties / tagline / description

Previous value: -"Frase corta de presentación."New value: +"Short pitch line."

changedOutput schema / properties / tags / description

Previous value: -"Etiquetas de la ficha."New value: +"Tags of the listing."

changedOutput schema / properties / url / description

Previous value: -"Dirección de la ficha en el idioma del token."New value: +"Address of the listing in the token's language."

changedOutput schema / properties / yours / description

Previous value: -"Solo con `found: false`: la plantilla existe, es tuya y aún no está publicada."New value: +"Only with `found: false`: the template exists, is yours and is not published yet."

First observedSep 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations are present, so the description carries the full burden. It discloses the read-only behavior, the limited response for own templates (`yours: true` with reviewStatus), and the dependency on token scope. It does not explicitly state side effects (none expected) or error handling, but for a read-only lookup this is sufficient.

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?

The description is moderately long but well-structured: primary purpose first, then constraints, then edge-case handling, then alternative tool. Every sentence adds necessary information without redundancy. It could be slightly shorter but remains efficient.

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 a single parameter, no annotations, and an output schema present, the description covers the key aspects: what it does, when to use it, limitations, and a pointer to the alternative. It omits potential error conditions (e.g., invalid slug) but these are likely handled by the schema or output structure. Overall it is complete enough for correct invocation.

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 schema already fully describes the slug parameter with 100% coverage. The description adds extra semantic context: slug refers to a catalog listing that must be published/approved, and mentions translated slugs work. This goes beyond the schema's simple 'Slug of the template' and clarifies the domain constraints.

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 clearly states the verb ('Returns') and resource ('full detail of a CATALOG template'), and lists specific fields (description, price, stack, rating, includes). It distinguishes itself from personal template tools by emphasizing 'CATALOG' and explicitly contrasting with my_templates for own templates. This makes the purpose unambiguous.

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?

It explicitly states when this tool applies (published and approved catalog listings) and when it does not (own templates not yet in catalog). It directly names the alternative (my_templates) and the condition for using it (seller scope). This provides clear routing guidance.

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

All Bernuvia 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?