Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Yes or no

yes_no
Read-only

A fair random yes or no, with a cryptographic random source. For quick decisions when the options are equally good. Use to break ties. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": "yes_no"
  }
}

Input Schema

NameRequiredDescriptionDefault
onlyNoOptional: comma-separated top-level result keys to keep, for a smaller answer (for example only=price,symbol); unknown keys are ignored and an empty match returns the full result

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare it read-only, non-destructive, non-open-world and non-idempotent. The description adds genuinely useful context outside the annotations: cryptographic randomness, a per-call price, 25 free calls, free failures, and the warning that repeats cost money. It omits what the response actually looks like, which matters given there is no output schema.

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?

The description is short and front-loads the core purpose before the pricing detail. There is mild redundancy between "Price $0.01/call" and "each call is charged, so repeats are not free," though the latter also conveys non-idempotency, so it mostly earns its place.

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 trivial single-output tool with no output schema and a fully documented parameter, the description covers purpose, cost, and side-effect profile. The one gap is that it hints at a structured result (via `only`) without saying the response is yes/no or what keys exist.

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?

There is only one optional parameter and the schema documents it at full coverage, including example values and behavior for unknown keys. The description adds nothing about the `only` projection filter, so the baseline of 3 applies.

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?

The description states a specific verb and resource: a fair random yes or no drawn from a cryptographic source. It conveys the decision-making scope ("quick decisions when the options are equally good"), but it never distinguishes itself from a sibling that performs an equivalent random pick (e.g. a coin flip), leaving the agent to infer the difference.

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 condition, namely tie-breaking when options are equally good. There is no explicit when-not guidance and no named alternative to route to, so it stops short of full routing instruction.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.