Skip to main content
Glama

effectiveness

Measures how often suggested coding patterns are reused to identify genuinely useful guidance versus noise for tuning pattern stores.

Instructions

Measure how often suggested patterns actually got used afterwards.

    For each pattern returned by suggest() in the window, checks whether
    it was observed again later. A high confirmation rate means the
    pattern is genuinely useful guidance; a low rate means it is noise
    that should be pruned.

    Use this to tune your store — patterns below a threshold may belong
    in alias_pattern() merges or gc() decay.

    Args:
        days: Look-back window in days. Default 30. Shorter windows
            surface recent drift; longer windows measure long-term value.

    Returns:
        Dict with keys: "window_days" (int), "patterns" (list of
        {pattern, suggested_count, confirmed_count, rate}), "overall_rate"
        (float 0.0-1.0 across all patterns).
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations provided, the description carries the full burden and does well by explaining the tool's behavior: it analyzes historical data from suggest() in a time window, calculates confirmation rates, and returns structured results. It mentions the tool's purpose for tuning and pruning, though it could add more on error handling or performance.

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 front-loaded with the core purpose, followed by usage guidance and detailed parameter/return explanations. Every sentence adds value—no redundancy or fluff—and it's structured logically for quick comprehension.

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's moderate complexity (1 parameter, no annotations, but with an output schema), the description is complete: it covers purpose, usage, parameter semantics, and behavioral context. The output schema handles return values, so the description appropriately focuses on higher-level context without redundancy.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, but the description fully compensates by explaining the 'days' parameter's purpose, default value, and effect (shorter vs. longer windows). It adds meaningful context beyond the schema's basic type and title, making the parameter's role clear.

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 the tool measures how often suggested patterns are later confirmed as useful, distinguishing it from siblings like suggest (which generates patterns), gc (which decays patterns), and alias_pattern (which merges patterns). It specifies the verb 'measure' and resource 'suggested patterns' with a clear outcome-focused purpose.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool ('to tune your store') and provides alternatives for low-rate patterns ('alias_pattern() merges or gc() decay'). It also distinguishes usage from suggest() by analyzing its output, offering clear guidance on context and exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yakuphanycl/instinct'

If you have feedback or need assistance with the MCP directory API, please join our Discord server