Skip to main content
Glama

agenttune

by com.agent-tune
OverviewDiscussionsAdmin

List all personality tunings

list_tunings
Read-only

Catalog of all 43 AgentTune personality tuning files (slug, code, name, one-line blurb), optionally filtered by system. Use it to resolve a user's personality type to the right slug before calling get_tuning.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
systemNoOptional filter: one of the five personality systems.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
licenseYes
tuningsYes
next_stepYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "license": {
+      "type": "string"
+    },
+    "next_step": {
+      "type": "string"
+    },
+    "tunings": {
+      "items": {
+        "properties": {
+          "blurb": {
+            "type": "string"
+          },
+          "body_url": {
+            "type": "string"
+          },
+          "canonical_url": {
+            "type": "string"
+          },
+          "code": {
+            "type": "string"
+          },
+          "evidence_status": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "revision": {
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "system": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "system",
+          "slug",
+          "canonical_url",
+          "body_url",
+          "revision",
+          "evidence_status"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "license",
+    "next_step",
+    "tunings"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces this by calling the tool a catalog and noting it returns 'all 43' files. It adds concrete behavioral context beyond annotations: the finite count, the fields returned, and the optional system filter, which sets expectations for a lightweight listing operation.

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?

Two sentences, front-loaded with the core purpose, followed by a practical usage note. No filler or redundant restatement of the schema; each sentence earns its place.

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?

For a read-only, optional-filter list tool with a complete parameter schema and an output schema, the description is sufficient. It tells the agent what is returned, when to use it, and how it relates to get_tuning, leaving no critical gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the only parameter 'system' is fully described in the schema with an explicit enum. The description merely mentions 'optionally filtered by system' without adding any semantic detail not already in the schema, so baseline 3 applies.

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 uses a specific verb ('Catalog') with a precise resource ('all 43 AgentTune personality tuning files') and enumerates the returned fields (slug, code, name, one-line blurb). It also names get_tuning as the downstream tool, differentiating itself from that sibling without ambiguity.

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?

The description gives an explicit usage directive: 'Use it to resolve a user's personality type to the right slug before calling get_tuning.' It does not explicitly list exclusions or alternatives like list_resources, but the primary intended workflow is clear.

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

All agenttune toolsInspect
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