Skip to main content
Glama

Show Varity Template Details

varity_template_info
Read-onlyIdempotent

Retrieve full details for a certified Varity template—required environment variables, resources, access mode, hardware profile, and certification state—by template ID.

Instructions

Show full details for a certified Varity template: required env, resources, access mode, hardware profile, and certification state.

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": {
      "template": "<template>"
    },
    "name": "varity_template_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
templateYesTemplate ID from varity_list_templates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description's real contribution is naming the returned fields, which is useful given there is no output schema. It says nothing about errors for missing/uncertified templates or any freshness/caching behavior.

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 compact sentence with the resource front-loaded and the payload enumerated in a short list. Every clause carries information; nothing is padding.

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 one-parameter read-only lookup with no output schema, enumerating the returned detail categories fills the main gap an agent would care about. Only minor items are missing: what happens when the template is not certified or the ID is invalid.

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?

Schema coverage is 100% and the single required parameter is fully documented in the schema, including its provenance ('Template ID from varity_list_templates'). The description does not add format or error semantics beyond that, so this sits at the baseline rather than above it.

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?

Uses a specific verb ('Show') and resource ('full details for a certified Varity template') and enumerates the detail categories (env, resources, access mode, hardware profile, certification state), so an agent knows exactly what it retrieves. It stops short of explicitly contrasting itself with varity_list_templates, though the schema's reference to that tool hints at the pairing.

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 template parameter says it comes 'from varity_list_templates', which suggests the list-then-inspect flow. There is no explicit statement of when to call this instead of the listing tool, no prerequisites, and no note about behavior on uncertified or unknown templates.

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