Convolut MCP Server

get_context_stats

Analyze context usage patterns with statistical metrics on counts, categories, and activity over specified time periods.

Instructions

Get statistical information about contexts including counts, categories, and usage metrics

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_context_stats"
  }
}

Input Schema

Name	Required	Description	Default
`date_range`	No	Time range for statistics	30d
`group_by`	No	How to group the statistics	category

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 27, 2025

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool retrieves statistical information but doesn't describe what format the statistics come in, whether there are rate limits, authentication requirements, or how the data is aggregated. For a statistical tool with zero annotation coverage, this leaves significant behavioral gaps.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the essential information about what statistical data is available.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a statistical retrieval tool with 2 well-documented parameters but no annotations and no output schema, the description provides basic purpose but lacks important context about return format, data aggregation methods, and behavioral characteristics. It's minimally adequate but has clear gaps in completeness.

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?

The input schema has 100% description coverage with clear enum values and defaults for both parameters. The description doesn't add any parameter-specific information beyond what's already documented in the schema. According to scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose as retrieving statistical information about contexts, specifying the types of data included (counts, categories, usage metrics). It uses a specific verb ('Get') and identifies the resource ('contexts'), but doesn't explicitly differentiate from sibling tools like 'list_contexts' or 'search_contexts' that might also provide contextual information.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'list_contexts' or 'search_contexts' that might also retrieve context information. It doesn't mention prerequisites, exclusions, or specific scenarios where statistical data is preferred over raw listings or searches.

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

Deploy Server