Skip to main content
Glama
vivashu27

SQL Injection MCP Server

by vivashu27

get_batch_result

Retrieve the detailed results of a previous batch SQL injection scan by providing its batch ID.

Instructions

Retrieve a previous batch scan result by ID.

Args: batch_id: Batch ID from a previous batch scan

Returns: Batch scan result details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
batch_idYes

Implementation Reference

  • The @mcp.tool() decorator registers get_batch_result as an MCP tool.
    @mcp.tool()
    def get_batch_result(batch_id: str) -> dict:
  • Handler function for get_batch_result tool - looks up a previous batch scan result by batch_id from the batch_results dictionary.
    def get_batch_result(batch_id: str) -> dict:
        """
        Retrieve a previous batch scan result by ID.
        
        Args:
            batch_id: Batch ID from a previous batch scan
        
        Returns:
            Batch scan result details
        """
        if batch_id in batch_results:
            return batch_results[batch_id]
        return {"error": f"Batch ID {batch_id} not found"}
  • batch_results dictionary used by get_batch_result to store and retrieve batch scan results.
    batch_results: dict[str, dict] = {}
Behavior3/5

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

The description indicates a read-only retrieve operation, but with no annotations provided, it lacks details on error handling, idempotency, rate limits, or other behavioral traits.

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 and front-loaded, with a clear main line followed by structured Args and Returns sections, containing no superfluous content.

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 simple retrieval tool with one parameter and no output schema, the description covers the basic usage and input source, though it omits error handling details. It is adequate given the complexity.

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?

With 0% schema coverage, the description compensates by explaining the batch_id parameter as 'Batch ID from a previous batch scan,' adding meaningful context beyond the schema's type definition.

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 'Retrieve a previous batch scan result by ID,' using a specific verb and resource, and distinguishes from siblings like get_scan_result.

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?

The description implies usage after a batch scan by indicating the batch_id comes from a previous batch scan, but it does not explicitly state when to use this tool versus alternatives or provide exclusion criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vivashu27/SQLinjector_MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server