Skip to main content
Glama
Sign In

Veynod

by io.github.veynod
OverviewDiscussionsAdmin

Acquire Resource

acquire_resource

Take a slot of a scarce resource as a lease (heartbeat it like a task lease). When full and queue=true you get queue_position and queue_ticket; on your turn a resource.granted event arrives and you must call again with queue_ticket within 60 s, or the slot goes to the next in line.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "resource_key": "<resource_key>"
    },
    "name": "acquire_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
queueNo
ttl_secondsNo
queue_ticketNo
resource_keyYes
wait_secondsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only say it is a non-read-only, non-destructive operation; the description adds the real behavioral substance — this is a time-boxed lease with heartbeat semantics, an asynchronous grant event, and a hard 60-second reclaim window that forfeits your place. It omits what happens on TTL expiry and the corresponding release_resource obligation.

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?

Three tightly packed sentences, front-loaded with the core action and then the failure/queue path. No filler; the only cost is that the density makes the ticket-retry rule easy to skim past.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

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 event-driven follow-up call is well covered. But a lease tool with 0% parameter documentation leaves two of five parameters (ttl_seconds, wait_seconds) undefined anywhere, which is a real gap for an agent building the call.

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 description coverage is 0% across five parameters, so the description carries the burden and only partially does: it explains queue and queue_ticket semantics well but never mentions ttl_seconds or wait_seconds, nor the wait/queue interaction or the 25-second wait cap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource with a precise mental model: "Take a slot of a scarce resource as a lease." That is far more than a restatement of the name and immediately separates it from siblings like release_resource and list_leases, though neither is named explicitly.

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 actionable runtime guidance: with queue=true you receive queue_position and queue_ticket, and on a resource.granted event you must re-call with the ticket within 60 s. It does not name alternatives or state when to prefer a non-queued acquisition versus giving up, so it stops short of full routing guidance.

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

All Veynod 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