security-framework-mcp

Overview Schema Source Related Servers Discussions Admin

get_top10

Read-onlyIdempotent

Retrieve OWASP Top 10 2021 security risks and their CWE mappings. Optionally filter by item ID to get details for a specific risk.

Instructions

Get OWASP Top 10 2021 items with CWE mappings.

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

Input Schema

Name	Required	Description	Default
`id`	No	Top 10 item ID, e.g. 'A01:2021'. Omit to list all.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0May 26, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true and idempotentHint=true, ensuring safe, idempotent operation. The description adds that it returns items with CWE mappings, providing useful behavioral detail beyond the structured annotations. No contradictions.

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?

A single, front-loaded sentence that contains no extraneous words. Every word is necessary and immediately conveys the tool's purpose.

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?

Given the tool's low complexity (one optional parameter) and the presence of an output schema (not shown but noted), the description covers the essential information. It could mention that it retrieves from an embedded dataset, but overall it is sufficient for an agent to understand the tool's function.

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% for the single parameter 'id', which is already described in the schema (e.g., 'e.g. A01:2021. Omit to list all.'). The description does not add any additional semantics for the parameter beyond what the schema provides, so baseline score of 3 is appropriate.

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?

The description clearly states the verb 'Get', the resource 'OWASP Top 10 2021 items', and specifies the inclusion of 'CWE mappings'. This distinguishes it from sibling tools like 'get_api_top10' and 'get_llm_top10' by specifying the year and added context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus other similar tools (e.g., get_api_top10, get_llm_top10). No mention of prerequisites or when not to use it. The agent is left to infer context from the name alone.

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