list_charactersThe characters an Alpy video can be drawn with: Alpy's own cast, and the creator's saved characters. Pass a character's id and source to create_video. Needs a connected Alpy account or an Alpy API key.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| alpy | Yes | ||
| saved | Yes | ||
| tones | Yes | ||
| voices | Yes |
Changes observed during successful MCP inspections.
Output schema / properties / alpy / items / properties / image_urlAdded value: +{
+ "description": "The character's drawing, as Alpy draws it. Show this, never a picture from elsewhere.",
+ "type": [
+ "string",
+ "null"
+ ]
+}Output schema / properties / alpy / items / requiredPrevious value: -[
- "source",
- "id",
- "name",
- "good_for",
- "about"
-]New value: +[
+ "source",
+ "id",
+ "name",
+ "good_for",
+ "about",
+ "image_url"
+]Output schema / properties / alpy / items / properties / image_urlRemoved value: -{
- "description": "The character's drawing, as Alpy draws it. Show this, never a picture from elsewhere.",
- "type": [
- "string",
- "null"
- ]
-}Output schema / properties / alpy / items / requiredPrevious value: -[
- "source",
- "id",
- "name",
- "good_for",
- "about",
- "image_url"
-]New value: +[
+ "source",
+ "id",
+ "name",
+ "good_for",
+ "about"
+]Output schema / properties / alpy / items / properties / image_urlAdded value: +{
+ "description": "The character's drawing, as Alpy draws it. Show this, never a picture from elsewhere.",
+ "type": [
+ "string",
+ "null"
+ ]
+}Output schema / properties / alpy / items / requiredPrevious value: -[
- "source",
- "id",
- "name",
- "good_for",
- "about"
-]New value: +[
+ "source",
+ "id",
+ "name",
+ "good_for",
+ "about",
+ "image_url"
+]Output schema / properties / alpy / items / properties / image_urlRemoved value: -{
- "description": "The character's drawing, as Alpy draws it. Show this, never a picture from elsewhere.",
- "type": [
- "string",
- "null"
- ]
-}Output schema / properties / alpy / items / requiredPrevious value: -[
- "source",
- "id",
- "name",
- "good_for",
- "about",
- "image_url"
-]New value: +[
+ "source",
+ "id",
+ "name",
+ "good_for",
+ "about"
+]Output schema / properties / alpy / items / properties / image_urlAdded value: +{
+ "description": "The character's drawing, as Alpy draws it. Show this, never a picture from elsewhere.",
+ "type": [
+ "string",
+ "null"
+ ]
+}Output schema / properties / alpy / items / requiredPrevious value: -[
- "source",
- "id",
- "name",
- "good_for",
- "about"
-]New value: +[
+ "source",
+ "id",
+ "name",
+ "good_for",
+ "about",
+ "image_url"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds value beyond them by disclosing the auth requirement (connected account or API key), which an agent needs before invoking. It does not describe pagination or result size, but the safety/behavior profile is well covered.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences, front-loaded with what the tool returns, then how to use the result and the auth prerequisite. No filler or redundant restatement of the title.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be spelled out, and the description covers purpose, downstream usage, and auth. It omits any pagination or ordering hints, which is a minor gap for a zero-parameter list tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes no parameters, so the baseline is 4. The description mentions that returned characters carry an 'id' and 'source', which adds useful meaning about the payload shape beyond the empty schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the resource: the two categories of characters (Alpy's own cast and the creator's saved characters) that a video can be drawn with. The name carries the 'list' verb, and the mention of create_video distinguishes it from sibling tools. It stops just short of an explicit verb-and-scope sentence but is easy to select correctly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives clear downstream context ('Pass a character's id and source to create_video') and a prerequisite (connected Alpy account or API key). It doesn't state when not to use it or name an alternative listing tool, but the usage context is unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.