Skip to main content
Glama
Sign In
codesafe-audit-mcp

codesafe-audit-mcp

by windhxy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

codesafe_list_bugs

Review security defects by paging through CodeSafe audit results, with optional severity and rule filters.

Instructions

Page through defect instances.

NOTE: the server endpoint ignores level/ruleCode filtering, so when those are supplied the filter is applied client-side to this single page only (returned count may be < page_size). For a complete filtered set, use codesafe_bug_summary + codesafe_audit_by_rule.

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": {
      "task_id": "<task_id>"
    },
    "name": "codesafe_list_bugs"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNo
task_idYes
page_sizeNo
rule_codeNo
page_indexNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Since no annotations are provided, the description carries the full burden. It discloses a key behavioral trait: the server ignores level/ruleCode filtering, so filters are applied client-side to a single page, possibly returning fewer than page_size results. This is beyond what the schema or name conveys. However, it does not mention permissions, safety, or return structure, which would be expected without annotations.

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?

The description is concise: a single line overview followed by a focused NOTE. It front-loads the core action and then delivers critical caveat and alternative usage in two sentences. No wasted words.

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?

The description covers the main behavioral caveat, points to alternatives, and provides missing context about filtering. Although it omits some parameter details, the output schema is present and the tool is a straightforward paginated list, so the overall context is sufficient for effective use.

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 must compensate. It clarifies that level and rule_code are filters (and explains their client-side limitation), and it mentions 'single page' and 'page_size' which relate to pagination. However, it does not explain task_id, page_index, or their roles, leaving gaps in parameter understanding.

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 opens with 'Page through defect instances,' which clearly specifies the action (paging) and resource (defect instances). It distinguishes this tool from siblings by noting the filtering limitation and recommending alternatives for complete filtered sets.

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

Usage Guidelines5/5

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

The description provides explicit guidance: 'For a complete filtered set, use codesafe_bug_summary + codesafe_audit_by_rule.' This tells the agent when not to use this tool and names specific alternatives, which is exactly what usage guidelines should do.

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

Deploy Server

Other Tools