website-search

aidefense_get_matrix

Read-onlyIdempotent

Get the structured AI Defense Matrix: 8 AI-specific asset rows x 6 NIST CSF 2.0 function columns. Each cell describes a control category for defending that asset class. Supports optional filtering by asset or function. This server never requests your program docs or product roadmap and instructs your AI to keep them local—the matrix, framework alignments, and playbooks flow to your AI for local analysis.

Input Schema

TableJSON Schema

Name	Required	Description
`asset`	No	Optional: filter to one asset class (e.g., 'ai-model', 'training-data'). Returns the 6 cells for that row.
`format`	No	structured: typed JSON of assets, functions, and cells (default). markdown: human-readable rendering grouped by asset.
`function`	No	Optional: filter to one NIST CSF function ('govern', 'identify', 'protect', 'detect', 'respond', 'recover'). Returns the 8 cells for that column.

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering safety. The description adds valuable behavioral context: it never requests program docs or product roadmap, instructs the AI to keep them local, and describes the data flow (matrix, alignments, playbooks) to the AI. This exceeds the structured annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, with the first sentence front-loaded with core purpose and structure. The second sentence adds privacy/flow context that earns its place for transparency, though it slightly extends beyond immediate tool-selection needs.

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 read-only retrieval tool with only optional parameters and no output schema, the description covers matrix content, filtering capabilities, and privacy behavior. It does not detail the exact JSON return shape, but the parameter schema and annotations fill in the remaining gaps adequately.

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%, with each parameter having an enum and description. The description's mention of 'optional filtering by asset or function' merely echoes the schema and adds no new semantic detail, so a baseline score is appropriate.

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 retrieves the 'structured AI Defense Matrix' with specific dimensions (8 asset rows x 6 NIST CSF 2.0 function columns) and describes cell content. This distinguishes it from sibling tools like cross_map or framework_alignment, using a specific verb and resource.

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?

No explicit guidance on when to use this tool versus alternatives such as aidefense_cross_map or get_framework_alignment. It implies usage for obtaining the matrix and mentions filtering, but does not state exclusions or alternative scenarios, leaving the agent to infer.

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

All website-search tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

Each tool has a distinct domain prefix (assessment, cti, ir, malware, vuln, product) that makes its purpose clear, and overlapping tools like get_template and get_brief_template are explicitly described as standalone variants. However, the large number of similarly structured tools (get_guidelines, load_context, get_frameworks) across six domains could still cause an agent to reach for the wrong domain's tool without close attention.

Naming Consistency5/5

Tool names follow a highly consistent snake_case pattern: domain_get_* (e.g., ir_get_template, cti_get_guidelines), domain_load_context, domain_review_report, and domain_get_cross_server_routes. The few exceptions like product_compare_context and search_zeltser still match the general verb-first or domain-first style, so the overall naming scheme is predictable and readable.

Tool Count2/5

With 53 tools, the server is far too large for its stated purpose of 'website search.' The vast majority of tools are not about search but rather about writing guidelines, templates, and scoring rubrics for multiple report domains (assessment, CTI, IR, malware, vuln, product) plus an AI defense matrix. The count is inflated by repeating the same set of ~7 tools for six different domains, making it feel bloated and hard to navigate.

Completeness4/5

For the broad coaching/report-writing scope, coverage is thorough: every domain has a template, guidelines, context loader, review criteria, and frameworks, plus generic writing guidance and rating tools. The actual search capability is minimal (search_zeltser, get_article, get_index_info) but adequate for the core task; a notable gap is the lack of a tool to list or browse all articles, which would make discovery easier.

Resources

Need Help?