Skip to main content
Glama

suggest_rules

Mine repeated corrections, stated preferences, and rejected tool calls into candidate rules for CLAUDE.md, AGENTS.md, or GEMINI.md, with evidence and whether each is already documented.

Instructions

Mine your repeated corrections ("no, use pnpm"), stated preferences ("always run ruff first") and rejected tool calls into candidate rules for CLAUDE.md / AGENTS.md / GEMINI.md, with evidence and whether each rule is already documented. Pass project="" to search all projects.

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": "suggest_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNo
sourcesNoall
days_backNo
min_sessionsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full load. It does disclose useful behavior — each candidate comes with evidence and a flag for whether the rule is already documented — and 'suggest' implies no mutation, but permissions, indexing prerequisites, and cost/latency are unstated. With an output schema present, return values needn't be explained, which keeps this at an adequate 3.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, front-loaded with the core action and its outputs, with the parameter note last. No filler, though the phrase 'mine your repeated corrections' with an example could be tightened.

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?

The description conveys the essential purpose and what the output contains, and the output schema covers the return shape. However, for a 4-parameter tool with zero schema coverage and no annotations, leaving three parameters undefined is a meaningful completeness gap for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0% across 4 parameters, so the description must compensate and largely does not. It explains only the project parameter (empty string means all projects); sources, days_back (default 90), and min_sessions (default 2) remain opaque — an agent cannot tell what 'sources' accepts or what counts toward min_sessions.

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 names a specific verb+resource: mining corrections, stated preferences, and rejected tool calls into candidate rules for CLAUDE.md/AGENTS.md/GEMINI.md. That scope differs implicitly from siblings like suggest_skills or suggest_instruction_updates, which target other artifacts, but no sibling is named explicitly, so it lands just short of a 5.

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?

Usage is implied rather than stated: the agent can infer it should call this when it wants rule suggestions, and 'Pass project="" to search all projects' guides one scoping decision. There is no when-not guidance and no routing to suggest_skills or suggest_instruction_updates for adjacent needs.

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