Skip to main content
Glama

mcpsense_checks

Read-only

Lists all registered scanner checks and their purposes from the current engine registry so you can understand available scan coverage before running checks.

Instructions

List every registered scanner check and its purpose using the current engine registry.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish this as a safe, closed-world read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description need not restate safety. It adds one useful fact — results come from the 'current engine registry,' i.e. a live source rather than a static hardcoded list — but says nothing about ordering, grouping, or the shape of each entry.

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 with the verb and scope first and no filler. The trailing clause about the engine registry carries real information rather than restating the name.

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?

For a zero-parameter, read-only enumeration tool with no output schema, the description conveys enough: what is listed and that each entry includes a purpose. It could say a little more about how entries are organized, but nothing blocking is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, which is the baseline-4 case: there is no parameter meaning left for the description to supply. Schema coverage is 100% and the description does not contradict or complicate the empty schema.

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?

States a specific verb and resource: 'List every registered scanner check and its purpose.' This clearly separates it from scan/verify/status siblings, which perform actions rather than enumerate the check catalog, though 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 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 guidance and no pointer to alternatives such as mcpsense_discover or mcpsense_status. The agent must infer that this is the reference/catalog lookup tool from the phrase 'every registered scanner check' alone.

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