Get statistics about the Sectora threat intelligence database including counts of EPSS scores, KEV entries, Nuclei templates, and exploits. No input required.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations; description fully covers behavior: stat retrieval, no inputs, lists included counts. Could mention idempotency, but adequate for a read-only stats tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences, front-loaded with action and resource, no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no parameters or output schema, description provides reasonable completeness: states what counts are included. Could specify output structure, but for a simple stat tool it is adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters; schema coverage 100%. Description reinforces 'No input required', which adds clarity. Baseline for 0 params is 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it gets statistics about the threat database and lists specific content types (EPSS, KEV, Nuclei, exploits). Differentiates from siblings like get_kev_recent (specific KEV entries) or get_trending_cves.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implicitly indicates usage with 'No input required', but lacks explicit when/when-not guidance or alternative recommendations compared to sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but 'lookup_cve' and 'get_weaponization_score' both focus on a single CVE, which could cause confusion. However, descriptions clarify their different outputs (full enrichment vs. numerical score).
Naming conventions are inconsistent: some tools use 'get_', others 'list_', 'lookup_', 'assess_', 'scan_url', 'search_cves'. No consistent verb_noun pattern across the set.
14 tools is well within the ideal 3-15 range, covering a broad scope of security assessment and intelligence without being excessive.
Core workflows (scanning, vulnerability lookup, threat stats) are covered, but missing update/delete operations for scans and domain verification tool. Notable gaps exist but core functionality is present.
