Skip to main content
Glama

Vendo AI

by com.vendo-ai
OverviewDiscussionsAdmin

Create a new agent

create_agent

Create an AI agent like step 1 of the app's builder. Choose its direction: purpose "sales" (default), "support" or "info". The agent starts in DRAFT and contacts nobody. Needs at least 1 credit on the balance (checked, not charged). Fails with a plan-limit error when all agent slots are used (see get_agent_plan_limits). Next: set_agent_company → generate_agent_script → channels.

Input Schema

NameRequiredDescriptionDefault
nameYesAgent's display name, e.g. 'Anna from Acme'
genderNoVoice/face gender (default female)
purposeNosales = sales agent, support = customer support, info = information assistant
descriptionNo1-2 sentences about what the agent does
avatar_presetNoPreset face avatar-1 … avatar-20 (male: 1,4,6,8,10-15; female: 2,3,5,7,9,16-20). For your own photo use set_agent_avatar_from_url afterwards

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / avatar_preset
      Added value: +{
+  "description": "Preset face avatar-1 … avatar-20 (male: 1,4,6,8,10-15; female: 2,3,5,7,9,16-20). For your own photo use set_agent_avatar_from_url afterwards",
+  "pattern": "^avatar-([1-9]|1[0-9]|20)$",
+  "type": "string"
+}
    • changedInput schema / properties / description / description
      Previous value: -"A short description of the agent itself (1-2 sentences, what it does)"New value: +"1-2 sentences about what the agent does"
    • addedInput schema / properties / gender
      Added value: +{
+  "description": "Voice/face gender (default female)",
+  "enum": [
+    "male",
+    "female"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / name / description
      Previous value: -"Agent's display name (e.g. 'Sales agent for Acme')"New value: +"Agent's display name, e.g. 'Anna from Acme'"
    • addedInput schema / properties / purpose
      Added value: +{
+  "description": "sales = sales agent, support = customer support, info = information assistant",
+  "enum": [
+    "sales",
+    "support",
+    "info"
+  ],
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "description"
-]New value: +[
+  "name"
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does so well: it discloses that the agent starts in DRAFT, contacts nobody, that the credit check is performed but not charged, and the exact plan-limit failure mode. It still omits what the response returns (e.g., the new agent ID) and any permission/role prerequisites.

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?

Front-loaded with the core action, then state, then constraints, then next steps — a sensible information order. It is dense but nearly every clause carries operational value; the 'like step 1 of the app's builder' analogy is the only slightly decorative phrase.

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 creation tool with no output schema and no annotations, this covers state, side effects, cost, failure mode, and follow-on calls. The one real gap is that it never tells the agent what object comes back, which matters since no output schema exists to compensate.

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%, so the schema already documents all five parameters and the baseline is 3. The description adds genuinely new information: the default for purpose is 'sales', which the enum description never states, and it signals that avatar can be set later via set_agent_avatar_from_url.

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?

States a specific verb and resource ('Create an AI agent'), names the builder step it corresponds to, and enumerates the direction values with a default. An agent can distinguish this from duplicate_agent or update_agent without opening any schema.

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?

Explicitly sequences the tool in a workflow ('Next: set_agent_company → generate_agent_script → channels') and routes plan-limit questions to get_agent_plan_limits. It does not say when to prefer duplicate_agent over creating from scratch, but the primary usage context is clear.

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

All Vendo AI 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