Skip to main content
Glama

Read the rules for working here, by topic

rules
Read-onlyIdempotent

Read the rules an agent works by here, one guide per topic, 3,000 to 11,000 characters each, 31,000 for all; without topic, the basics and an index. Read the one the instructions name before a first write of its kind.

Instructions

Read the rules an agent works by here, one guide per topic, 3,000 to 11,000 characters each, 31,000 for all; without topic, the basics and an index. Read the one the instructions name before a first write of its kind. Markdown syntax is language; how the app works, help.

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

Input Schema

NameRequiredDescriptionDefault
topicNoThe guide

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.47.1
    • changedInput schema / properties / topic / description
      Previous value: -"The guide; left out, the basics and the index"New value: +"The guide"
  2. Changed1 schema field changedv1.47.0
    • changedInput schema / properties / topic / enum
      Previous value: -[
      -  "tasks",
      -  "documents",
      -  "tidying",
      -  "all"
      -]New value: +[
      +  "tasks",
      +  "documents",
      +  "tidying",
      +  "ideas",
      +  "all"
      +]
  3. Changed2 schema fields changedv1.43.2
    • changedInput schema / properties / topic / description
      Previous value: -"tasks, documents or tidying for that guide; all for every rule at once; left out, the basics and the index. general is what all gave before tidying was split off"New value: +"The guide; left out, the basics and the index"
    • changedInput schema / properties / topic / enum
      Previous value: -[
      -  "tasks",
      -  "documents",
      -  "tidying",
      -  "all",
      -  "general"
      -]New value: +[
      +  "tasks",
      +  "documents",
      +  "tidying",
      +  "all"
      +]
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read, so the description's job is to add context, which it does: it discloses output size per topic (3,000–11,000 characters, ~31,000 for `all`) and the default payload when `topic` is omitted. That size disclosure is genuinely actionable for an agent managing context; it stops short of describing section structure or ordering.

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 dense sentences, front-loaded with purpose and cost, then routing. Every clause carries new information; the telegraphic 'Markdown syntax is `language`; how the app works, `help`' is terse but unambiguous in context.

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 read-only single-parameter tool with no output schema, the definition covers what the guides are, their size, the default behavior, and where adjacent topics live. Minor gaps — whether topics can change or how the guide is structured internally — are low-risk for correct invocation.

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?

Schema coverage is 100% and the enum is already enumerated, so the baseline would be 3. The description earns above baseline by explaining what the absent-parameter case returns (basics plus an index) and by attaching per-value cost to `all` versus individual topics — meaning the schema cannot express.

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 ('Read the rules an agent works by here') and immediately scopes it to one guide per `topic`. It also explicitly separates itself from two siblings: Markdown syntax belongs to `language`, and how the app works belongs to `help`, so an agent can route without opening other schemas.

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?

Gives a concrete trigger — read the topic the instructions name before a first write of its kind — and names the alternatives for adjacent needs (`language`, `help`). It does not say when reading is unnecessary or whether re-reads are ever needed, which keeps it short of fully explicit.

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