Skip to main content
Glama

Check Security Issues

check_security
Read-onlyIdempotent

Scans Java source code for common security issues such as injection flaws and weak cryptography, helping developers identify risky patterns before deployment.

Instructions

Scan Java source for common security issues such as injection and weak crypto.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "code": "<code>"
    },
    "name": "check_security"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesSource code to check for security issues
languageNoProgramming language

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that this is a static source scan with a defined issue category set, but says nothing about output format (findings per line? severity?), scan limits, or whether it flags or fixes.

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 resource scope first and examples second; nothing is redundant or padded.

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

Completeness3/5

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

With only two fully documented parameters and annotations covering the safety profile, the definition is workable, but for a security scanner the agent still lacks any hint of what findings look like or whether the scan is limited to Java regardless of the language argument.

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 100% for both parameters, so the schema already documents `code` and `language`. The description adds no extra semantics, and its emphasis on "Java" is slightly narrower than the free-form language parameter the schema exposes.

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?

"Scan Java source for common security issues" gives a specific verb (scan), a specific resource (Java source), and concrete examples of what it finds (injection, weak crypto). It clearly differs from generic tools like analyze_code in stated intent, though it never names the sibling to reinforce the distinction.

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

Usage Guidelines3/5

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

Usage is only implied by the resource scope: use this when you have Java source and want a security-focused review. There is no explicit statement of when to prefer it over analyze_code or analyze_javascript, and no prerequisites or exclusions are given.

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