Skip to main content
Glama

List Available AI Agent Templates

varity_list_agents
Read-onlyIdempotent

List certified Varity templates from the gateway-owned catalog, providing a backward-compatible alias that avoids reliance on hardcoded MCP lists.

Instructions

Backward-compatible alias for varity_list_templates. Returns the gateway-owned certified template catalog, not a hardcoded MCP list.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv2.0.0-beta.24

TDQS

A3.6/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 fully covered structurally. The description adds one genuinely useful behavioral fact — that results come from a gateway-owned certified catalog rather than a hardcoded MCP list — but says nothing about ordering, pagination, deprecation/removal plans, or what the response looks like.

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?

Two short sentences, front-loaded with the alias relationship, which is the most decision-relevant fact. The trailing clause 'not a hardcoded MCP list' is slightly internal-facing but does earn its place by clarifying the data source.

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 zero-parameter, no-output-schema read tool with rich annotations, the description covers what is returned and where it comes from. The only meaningful gap is the absence of guidance on whether this alias is deprecated in favor of varity_list_templates.

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 tool takes zero parameters, so there is no parameter meaning to convey; the baseline for a parameterless tool is 4. The empty object schema with additionalProperties=false is consistent with the description's implication that no arguments are needed.

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?

The description uses a specific verb-resource framing ('Returns the gateway-owned certified template catalog') and identifies itself as an alias of the sibling varity_list_templates, so an agent can place it immediately. It loses a point because the actual resource — 'agents' vs. 'templates' — is only reconciled through the alias statement, not described in its own terms.

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?

'Backward-compatible alias' implies the canonical varity_list_templates should be preferred, but the description never states that explicitly, nor does it give any condition for choosing this tool over the canonical one. The routing signal is present but requires the agent to infer it.

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