Skip to main content
Glama

reports_checklist

Read-onlyIdempotent

Map an audit report to MASVS v2 or a custom checklist, assigning each item a status such as findings, partial, limited, not-run, or not-applicable—none treated as a pass.

Instructions

Map a report onto a checklist: masvs-v2 (built in) or a checklist TOML inside an MCP root that maps items to MASWE identifiers and APSA rules. Statuses are findings, partial, limited, no-findings-in-checked-scope, not-run, not-applicable or not-assessed; none is a pass.

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

Input Schema

NameRequiredDescriptionDefault
checklistNomasvs-v2
report_idNolatest

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.1

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare this a read-only, idempotent, non-destructive, closed-world call, so the safety profile is covered. The description adds genuinely useful semantics the annotations cannot: the full status vocabulary and the key warning that 'none is a pass', which prevents misreading 'no-findings-in-checked-scope' or 'not-assessed' as success. It says nothing about failure modes, such as what happens when an unknown checklist name is supplied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the core action and with zero filler. The status enumeration is long but each term is load-bearing for interpreting output; only the phrasing could be tightened into a list.

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?

An output schema exists, so return values need no prose, and the tool is a simple two-parameter read. The description covers the checklist source and result vocabulary, which is the hard part; the remaining gap is 'report_id' and default behaviour, which is minor but real.

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 0%, so the description carries the burden and does explain the 'checklist' parameter well: 'masvs-v2' is built in, otherwise a checklist TOML inside an MCP root mapping items to MASWE identifiers and APSA rules. The 'report_id' parameter is never mentioned, leaving the 'latest' default unexplained, so compensation is only partial.

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 opens with a specific verb and resource: 'Map a report onto a checklist', and narrows the scope by naming the built-in 'masvs-v2' checklist and TOML checklists living in an MCP root. It stops short of distinguishing this from siblings such as reports_get, reports_compare or policy_evaluate, so an agent must infer the boundary itself.

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?

There is no explicit when-to-use or when-not-to-use statement, and no sibling is named as an alternative. The available checklist sources are described, which implies the compliance-mapping use case, but nothing tells the agent why it should choose this over reports_get or policy_evaluate.

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