Skip to main content
Glama

yesno_random

Read-onlyIdempotent

Get a random yes/no answer with an animated GIF to quickly settle simple decisions or prompts, optionally forcing yes, no, or maybe.

Instructions

Get a random yes/no answer with an animated GIF.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "yesno_random"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoForce a specific answer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already carry the safety profile (readOnly, non-destructive, openWorld), so the description adds the one thing structured fields don't: the response includes an animated GIF, which matters since there is no output schema. Minor tension: 'random' implies each call differs, while idempotentHint=true suggests otherwise, though that is about side effects rather than output variance.

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 with zero filler; the core action comes first and the output detail follows. Nothing could be removed without losing information.

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 zero-required-parameter, no-output-schema tool, the description covers what it does and what it returns (a GIF), which is the main gap such tools usually have. It stops short of describing response fields or whether the GIF URL accompanies the answer.

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?

The single optional parameter has 100% schema coverage including an enum and the note 'Force a specific answer', so the baseline is 3. The description adds nothing about `force` (e.g., that it overrides randomness), leaving the schema to do all the work.

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?

States a specific verb and resource ('Get a random yes/no answer') plus the distinctive output form ('with an animated GIF'), so it is clearly separable from siblings like random_flip_coin, random_number, or random_pick_from_list. An agent knows exactly what this returns 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 Guidelines2/5

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

The description gives no when-to-use or when-not-to-use guidance and never mentions alternatives in a sibling set crowded with similar randomizers (random_flip_coin, random_pick_from_list, random_roll_dice). The intended use (casual decision-making) is only incidental to the phrasing.

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

Deploy Server

Other Tools