Skip to main content
Glama
Sign In
Renyi

Renyi

Official
by renyi-lang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

cheat_sheet

Read the complete Renyi language reference on one page before writing code: syntax, types, effects, and library usage.

Instructions

The whole Renyi language on one page (docs/cheatsheet.md): syntax, types, effects and the library. Read it before writing Renyi.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the underlying artifact path (docs/cheatsheet.md), implying a read-only documentation fetch, but does not confirm read-only behavior or describe the return shape. For a zero-parameter doc reader the behavior is largely self-evident, so this is adequate rather than rich.

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?

Two sentences, zero waste. The identity of the resource is front-loaded ahead of the prescriptive usage hint, and every clause 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?

With no parameters, no output schema, and no annotations, the definition is nearly self-sufficient: it says what the tool is and when to reach for it. The only unaddressed detail is the exact return format, which is minor for a static doc fetch.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so per the baseline there is nothing for the description to disambiguate. Schema coverage is reported at 100% with an empty property set, and the description correctly adds no spurious argument guidance.

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 concrete resource (the entire Renyi language cheatsheet at docs/cheatsheet.md) and enumerates its coverage: syntax, types, effects, and the library. This is clearly distinguished from the narrower sibling `library_lookup` by scope, though it does not explicitly contrast with `effects` or `definition`.

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?

"Read it before writing Renyi" gives a clear, actionable trigger for invoking the tool. There is no explicit when-not or named alternative, but the directive is unambiguous for an agent starting Renyi work.

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