Skip to main content
Glama

Cheat Sheet

cheat_sheet
Read-onlyIdempotent

OWASP Cheat Sheet Series, concise, practical defensive guidance. With a topic, returns the matching cheat sheet as Markdown (or candidate matches if ambiguous). Without a topic, lists all available cheat sheets.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "topic": "SQL Injection"
    },
    "name": "cheat_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoTopic or sheet name, e.g. "SQL Injection", "JWT", "password storage". Omit to list all sheets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "topic": "SQL Injection"
      +  },
      +  {}
      +]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: output is Markdown, ambiguous topics return multiple candidates, and the no-topic path returns a full catalog listing — important since no output schema exists.

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, each earning its place: the first identifies the corpus and its nature, the second enumerates both behavior modes in order of the primary parameter's presence or absence. No filler or redundant framing.

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?

This is a low-complexity, single-optional-parameter read tool with full annotation coverage, and the description explains both return shapes despite the absence of an output schema. Minor omissions — approximate sheet size or how many candidate matches may come back — are not blocking 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 single topic parameter is fully documented with examples, including 'Omit to list all sheets.' The description's mention of 'with a topic / without a topic' restates the schema rather than adding syntax or format detail, 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 names a specific resource — the OWASP Cheat Sheet Series — and states both retrieval modes: topic-based lookup returning Markdown, and a full listing when no topic is given. The OWASP branding implicitly separates it from sibling OWASP ASVS tools (asvs_chapters, asvs_requirements), but no sibling is named explicitly.

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 clearly frames the two invocation contexts (pass a topic to fetch a sheet, omit it to browse the catalog) and notes that ambiguous topics yield candidate matches rather than a single sheet. There is no explicit when-not or named alternative, so it stops short of full routing guidance.

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.