Skip to main content
Glama

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?").

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": {
      "level": 1,
      "chapter": "V6"
    },
    "name": "asvs_requirements"
  }
}

Input 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/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds that results are citable as a controls layer, which is genuinely useful context, but says nothing about ordering, total counts, or truncation behavior when the limit clips results.

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?

Three compact sentences: what it returns, how to filter, and why it matters, with the resource identification front-loaded. No filler or repetition of the title.

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 output schema, the description compensates by naming the fields each record carries, and it covers all filter dimensions. Minor gaps remain around result ordering, total counts, and how this relates to asvs_chapters for a multi-tool workflow.

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% and the schema already documents level semantics ('at or below this level'), chapter ids, query keywords and the default 40 / max 100 limit. The description adds no syntax or interpretation beyond that, so the baseline 3 applies.

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?

Names the specific resource (OWASP ASVS 5.0 testable security requirements) and enumerates the returned fields (verification id, section, level, text), plus a positioning phrase ('the citable controls layer'). An agent can distinguish this from the sibling asvs_chapters without opening either schema.

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 when-to-use framing with a worked example ('ground a control: what does ASVS require for password storage?') and lists the filter axes. It does not name an alternative or state when-not to use it (e.g. versus asvs_chapters for structure browsing), 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.