get_checks
The complete catalog of scanner checks: stable ids, layers, weights, tiers, and fix guidance. Check ids are stable — gate CI on explicit id lists.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
agentready
TDQS
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It explicitly notes that check IDs are stable and suggests gating CI on explicit ID lists, which is a valuable behavioral insight. However, it does not disclose other traits like idempotency, caching, or auth needs.
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?
Two concise sentences with no wasted words. The first sentence front-loads the purpose, and the second adds an essential behavioral insight. Every sentence earns its place.
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 the tool has no parameters and no output schema, the description provides a thorough list of what the catalog contains (ids, layers, weights, tiers, fix guidance). It also adds a practical note about stability. This is sufficient for an agent to understand the tool's output.
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?
The input schema has zero parameters, and schema description coverage is 100%. The description adds no parameter info, but with zero parameters the baseline is 4. The description does not need to explain parameters.
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 that the tool returns 'the complete catalog of scanner checks' with specific attributes (stable ids, layers, weights, tiers, fix guidance). It uses a specific verb-resource pair and inherently distinguishes from sibling tools like get_feedback or get_skill.
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 when one needs the full list of scanner checks, but it does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention cases where it should not be used.
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
Disambiguation4/5
Tools are generally well-distinguished, but discover_products and search_capabilities could be confused since both search across domains. The difference in query type (task intent vs. capability) is somewhat subtle. Overall, most tools have clear, separate purposes.
Naming Consistency5/5
All tool names use a consistent verb_noun pattern (e.g., discover_products, get_checks, scan_domain). The naming is predictable and matches the server's domain of evaluating agent-ready properties.
Tool Count5/5
With 11 tools, the server covers scanning, scoring, feedback, and search without being overly broad. Each tool has a distinct role, and the count is appropriate for the focused purpose of assessing agent readiness.
Completeness5/5
The tool set covers the full lifecycle: discover/scan domains, get scores and checks, apply skills, verify with challenges, submit feedback and disputes. There are no obvious missing operations for the stated domain.