Skip to main content
Glama
Sign In

iDos Games

by com.idosgames
OverviewDiscussionsAdmin

Pin Jev knob

tuning_pin

Pin or unpin a knob. The decision model never changes a pinned knob (a hand edit in the dashboard pins it by itself). Only unpin when the publisher asks.

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": {
      "title_id": "<title_id>",
      "knob_id": "<knob_id>",
      "pinned": "<pinned>"
    },
    "name": "tuning_pin"
  }
}

Input Schema

NameRequiredDescriptionDefault
pinnedYestrue = pin, false = unpin.
knob_idYesKnob id.
title_idYesTitleID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

The annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so they establish this is a safe, non-destructive mutation but say nothing about consequences. The description adds real value by disclosing that pinned knobs are exempt from the decision model and that a dashboard hand edit pins automatically, which tells the agent the setting has lasting effects. It does not say what happens when pinning an already-pinned knob (idempotency) or 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?

Three short sentences, zero filler, with the operation stated first and the rationale and constraint following. Every sentence carries information the agent cannot get from the schema or annotations.

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 three-parameter, all-required mutation with full schema coverage and annotations covering the safety profile, the description is close to sufficient. The only missing pieces are edge-case behavior (pinning an already-pinned knob) and whether the new state is returned, neither of which is critical for correct invocation.

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%, and the `pinned` boolean is already documented as "true = pin, false = unpin." The description adds no per-parameter meaning beyond that, so the baseline of 3 applies when the schema carries the semantics.

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 opens with a specific verb pair and resource: "Pin or unpin a knob." That is enough to separate it from the tuning_* siblings (apply, preview, reroll, surprise, undo), which all imply different operations on the same object.

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 gives a clear when-to-use rule for the destructive direction: "Only unpin when the publisher asks." It also explains the state that makes pinning matter (the decision model will not touch a pinned knob), which frames the decision. It stops short of naming an alternative tool for adjacent needs, so it is not a full when/when-not/alternative treatment.

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

All iDos Games 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