Skip to main content
Glama

VNyan triggers

vnyan_trigger

Manage VNyan triggers globally: call or queue trigger executions, reset queues, and retrieve recently observed trigger calls with optional text and numeric parameters.

Instructions

Call, queue, or reset VNyan's named Triggers (global across all node graphs - a TriggerNode with this name fires), and read recently-observed trigger calls. Source: plugin (live, read+write). 'recent' only sees calls made since the plugin loaded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoTrigger name (required for call/enqueue)
limitNoMax entries for 'recent' (default 50)
queueNoQueue name (required for enqueue/resetQueue)
text1NoText param 1 - a free string, use this for decimals/precise values
text2NoText param 2 - a free string
text3NoText param 3 - a free string
actionYesWhich trigger operation to perform
value1NoNumeric param 1, passed to the TriggerNode as a whole INTEGER (truncates fractions - e.g. 2.5 arrives as 2). For a precise decimal, use text1-3 instead and convert on the receiving end with a TextToDecimalNode (see vnyan_guide topic:'node-authoring').
value2NoNumeric param 2 - same int-truncation caveat as value1
value3NoNumeric param 3 - same int-truncation caveat as value1
waitTimeAfterMsNoFor 'enqueue': milliseconds to wait after this item runs before the queue dequeues the next one.
Behavior4/5

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

Despite no annotations, the description discloses key behaviors: integer truncation for numeric parameters, recommendation to use text for decimals, explicit explanation of 'enqueue' behavior with waitTimeAfterMs, and the limited scope of 'recent'. Does not mention error handling or side effects, but covers main behavioral traits well.

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?

Description is brief but packs essential information. Three sentences cover purpose, source liveness, and scoping. Could be slightly restructured with bullet points, but current format is efficient and easy to parse.

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?

Given 11 parameters and no output schema, the description explains key usage details like integer truncation and enqueue semantics. Lacks return value explanation and error cases, but overall adequate for a well-schematized tool.

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 has 100% coverage with detailed descriptions. The description adds extra meaning: explains integer truncation caveat, recommends text params for precision, and gives usage guidance for 'enqueue' wait time. This goes beyond what the schema alone provides.

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?

Description clearly states multiple actions (call, queue, reset, read) on the resource 'VNyan's named Triggers', and adds crucial context that triggers are global across all node graphs. This distinguishes it from sibling tools like vnyan_param or vnyan_api_fire.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. The description mentions that triggers are global and 'recent' is only since plugin load, but does not compare with other tools like vnyan_param (for parameters) or vnyan_api_fire (for direct API calls).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/seth-rah/vnyan-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server