Skip to main content
Glama
Sign In
opencti-mcp

opencti-mcp

by scriptedstatement
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_cache_stats

Retrieve cache hit rates, sizes, and evictions to diagnose issues and optimize performance.

Instructions

Get cache statistics including hit rates, sizes, and evictions. Useful for debugging and performance tuning.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_cache_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It describes what the tool returns and frames it as non-destructive by using 'Get,' but it does not explicitly state whether the call has side effects, requires special permissions, or reflects real-time vs. cached values. This is adequate but not detailed.

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 short sentences with no wasted words. The core resource and output content are front-loaded, and the use case is stated succinctly.

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 no-parameter, no-output-schema tool, the description is reasonably complete: it names the resource, the key statistic categories, and a practical use case. It could be more precise about formats or which cache is being queried, but the low complexity means these are minor gaps.

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 tool has zero parameters, so there is nothing for the description to explain. The schema description coverage is trivially 100%, and the baseline of 4 is appropriate for a no-parameter tool.

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 a specific verb and resource: 'Get cache statistics.' It also enumerates the exact kinds of data returned (hit rates, sizes, evictions), which makes the tool's purpose concrete and differentiates it from sibling search and status 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 gives clear usage context: 'Useful for debugging and performance tuning.' It does not mention alternatives or exclusions, but the tool has no parameters and a unique resource, so the implied when-to-use guidance is sufficient.

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

Deploy Server

Other Tools