list_suites
List all 16 suites in the SaferAgenticAI framework (9 drivers + 7 inhibitors) with subgoal counts and titles. Call this first to orient.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
saferagenticai-mcp
TDQS
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries full burden; it fully discloses the read-only nature, expected output (suites with counts and titles), and its role as an initial orientation tool.
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 that conveys all essential information without extraneous words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no parameters, no output schema, and no annotations, the description is fully complete, covering what, why, and when to use.
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 zero parameters and 100% schema coverage, the description adds meaning by explaining the return content and purpose, exceeding the baseline of 4.
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 specifies the exact content (16 suites, 9 drivers, 7 inhibitors) and includes subgoal counts and titles, clearly differentiating from sibling 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?
Explicitly says 'Call this first to orient,' providing clear guidance on when to use the tool, though no when-not-to-use is given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4/5.0
Disambiguation5/5
Each tool has a distinct purpose: finding patterns, cross-references, operational heuristics, requirements, listing, searching, and review stats. Overlap is minimal and well-differentiated by input parameters.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case, e.g., find_patterns_for_task, list_requirements, resolve_id. No mixing of conventions or vague verbs.
Tool Count5/5
12 tools cover core operations (list, get, search, resolve, review) for the framework domain without bloat. Each tool serves a clear, non-redundant purpose.
Completeness4/5
Covers most needed operations for exploring the framework: listing suites, searching patterns, getting details, cross-references, review stats. Lacks a direct 'list all patterns' tool, but list_requirements and search_patterns partially fill that gap.