Skip to main content
Glama
MichaelEnny

healthsec-mcp

by MichaelEnny

generate_security_report

Compile a structured security report from clinical AI model evaluation results, marking untested sections as not evaluated and providing a deployment recommendation only when a Security Posture Score is supplied.

Instructions

Compose a structured security report from whichever tool outputs you have.

    Pass the raw dict returned by any subset of run_fgsm,
    run_boundary_attack, run_membership_inference,
    assess_attack_coverage, check_rbac, score_audit_completeness,
    score_compliance, and compute_sps. Sections you didn't run are
    marked "not evaluated", never silently assumed to pass. A
    deployment recommendation only appears if `sps` (compute_sps's
    own output) is supplied -- it is never inferred from partial
    results.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spsNo
fgsmNo
rbacNo
boundaryNo
complianceNo
attack_coverageNo
audit_completenessNo
membership_inferenceNo
Behavior5/5

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

No annotations are provided, so the description carries full burden. It discloses key behaviors: sections not run are marked 'not evaluated', deployment recommendation only appears if sps is supplied, never inferred. This is thorough and honest.

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 two paragraphs, front-loaded with purpose, and every sentence provides necessary information without waste. It is well-structured and easy to parse.

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?

Given 8 optional parameters and no output schema, the description provides good context for inputs but lacks details on the output format (e.g., JSON, Markdown). While 'structured security report' is mentioned, the agent might need more specifics about the return value.

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% and parameters are untyped objects. The description adds meaning by linking parameters to tool outputs (e.g., 'fgsm' from run_fgsm) and explains the special role of 'sps'. However, the mapping from parameter names to tool names is implicit and could be clearer.

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 it composes a structured security report from outputs of specific sibling tools, listing them explicitly and explaining how missing sections are handled. This distinguishes it from individual assessment tools.

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

Usage Guidelines4/5

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

The description explains to pass raw dicts from any subset of the listed tools. It also clarifies constraints (no silent assumptions, deployment recommendation only with sps). While it doesn't explicitly state when to use alternatives, the purpose is clear.

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/MichaelEnny/healthsec-mcp'

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