Skip to main content
Glama

Owasp

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Asvs Requirements

asvs_requirements
Read-onlyIdempotent

Testable security requirements from OWASP ASVS 5.0, each with its verification id (e.g. "V6.2.1"), section, level (L1/L2/L3) and text — the citable controls layer. Filter by chapter, level and/or keyword. Use to ground a control ("what does ASVS require for password storage?").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
levelNoAssurance level: 1 (essential), 2 (standard), 3 (advanced). Returns requirements applicable at or below this level.
limitNoMax requirements to return (default 40, max 100).
queryNoKeyword filter on requirement text, e.g. "password", "TLS", "CSRF".
chapterNoChapter id like "V6" (Authentication). Omit to search all chapters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "chapter": "V6",
+    "level": 1
+  },
+  {
+    "level": 2,
+    "limit": 20,
+    "query": "password"
+  }
+]
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds no contradicting or additional behavioral traits beyond filtering capability, which is acceptable given annotation coverage.

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 efficiently convey tool purpose, contents, and usage example. Front-loaded with key information, no extraneous text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Without output schema, description adequately explains return structure (verification id, section, level, text). Also covers filtering options. Combined with rich annotations and schema, tool is well-specified.

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 coverage is 100% with good descriptions. Description provides example usage and clarifies enum values (L1/L2/L3) and example id format, but adds limited new meaning beyond schema.

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?

Description clearly identifies the tool as providing testable security requirements from OWASP ASVS 5.0 with specific fields (verification id, section, level, text). It distinguishes from sibling 'asvs_chapters' by focusing on individual requirements and filtering.

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?

Implies use case for grounding controls ('what does ASVS require for password storage?') and mentions filter options. Does not explicitly state when to avoid or name alternatives, but context is sufficient.

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

All Owasp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources