Skip to main content
Glama
Sign In

Voidless

by dev.voidless
OverviewDiscussionsAdmin

tag_asset

DestructiveIdempotent

Add, remove or replace the tags on an asset, so it can be found again with list_assets(tag). Free.

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": {
      "id": "<id>",
      "tags": "<tags>"
    },
    "name": "tag_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAsset ID (from list_assets / get_asset or a previous result)
modeNoadd = keep existing tags and add these, remove = drop these, replace = set exactly theseadd
tagsYesTags, e.g. ['player', 'level-1']. Case-insensitive duplicates are merged

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description's one genuine addition beyond annotations is 'Free', signaling no credit cost, but it does not elaborate on replace wiping existing tags (that detail lives only in the mode schema) or on what the call returns.

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?

A single front-loaded sentence states the operation and its payoff, with 'Free.' appended as a compact cost signal. There is no redundant or filler wording.

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?

For a simple 3-parameter mutation, the description covers purpose and cost but says nothing about the result shape or partial-failure behavior, and there is no output schema to fall back on. Adequate but leaves gaps an agent would want for a destructive operation.

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 100%, including an explicit enum explanation for mode and case-insensitive dedup semantics for tags, so the baseline of 3 applies. The description adds no format, limit, or value guidance beyond what the schema already documents.

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 set (add, remove, replace) applied to a specific resource (tags on an asset), which is directly distinguishable from the sibling tag_frame (which operates on frames) and from list_assets. An agent can identify the operation without opening the schema.

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

Usage Guidelines3/5

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

It gives the motivating context ('so it can be found again with list_assets(tag)'), which implies when to use it, but offers no explicit when-not guidance and never mentions tag_frame as the alternative for frames or how mode selection should be decided.

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

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