Skip to main content
Glama

Vendo AI

by com.vendo-ai
OverviewDiscussionsAdmin

Set the contacts the agent hands out

set_agent_contact_channels

Set the meeting link, presentation link, email, phone, WhatsApp, Telegram and up to 10 custom links that the agent gives to visitors (also shown as screen cards). MERGE: only the channels you pass change; pass "" (or null for custom_links) to clear one. Write, free.

Input Schema

NameRequiredDescriptionDefault
idYesAgent id (UUID) — from list_agents
emailNo
phoneNo
telegramNo
whatsappNo
meeting_urlNoBooking link, e.g. Calendly (http/https)
custom_linksNoReplaces the whole custom link list; null or [] clears it
presentation_urlNoLink to a presentation/deck (http/https)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / custom_links
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "label": {
+            "maxLength": 60,
+            "type": "string"
+          },
+          "note": {
+            "description": "When the agent should share it",
+            "maxLength": 200,
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "label",
+          "url"
+        ],
+        "type": "object"
+      },
+      "maxItems": 10,
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Replaces the whole custom link list; null or [] clears it"
+}
    • changedInput schema / properties / id / description
      Previous value: -"Agent id"New value: +"Agent id (UUID) — from list_agents"
    • changedInput schema / properties / meeting_url / description
      Previous value: -"Booking link, e.g. Calendly"New value: +"Booking link, e.g. Calendly (http/https)"
    • addedInput schema / properties / presentation_url
      Added value: +{
+  "description": "Link to a presentation/deck (http/https)",
+  "type": "string"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses that this is a write operation, that it is free, that updates are merged rather than replaced, and how to clear a channel. It also notes custom links are limited to 10 and appear as screen cards, though it does not cover permission prerequisites or response 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?

The description is front-loaded with the tool's purpose, then immediately follows with the critical merge/clear semantics. Every clause adds useful information without repetition or filler.

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 an 8-parameter mutation tool with no annotations and no output schema, the description gives an agent enough to invoke it correctly: which channels exist, merge behavior, clearing rules, and the custom-link cap. The main omission is that it does not mention the required agent id, though the schema documents that.

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 description adds meaning beyond the schema by naming each channel type and explaining merge/clear semantics, including empty-string clearing and null for custom_links. Schema coverage is only 50%, and the description does not mention the required id parameter, but it covers the semantically important parameters well.

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 states a specific verb and resource: it sets the meeting link, presentation link, email, phone, WhatsApp, Telegram, and custom links that the agent gives to visitors. Enumeration of exact channel types distinguishes it from sibling setters like set_agent_company, set_agent_voice, and set_agent_integrations.

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?

It clearly explains the merge behavior, which is the key usage rule for this setter: only passed channels change, and passing an empty string or null clears a channel. It does not explicitly name alternatives such as update_agent or state when to avoid this tool, so it falls short of full alternative guidance.

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