Skip to main content
Glama

find_friction_patterns

Finds recurring friction patterns across past sessions—repeated file reads, failing commands, correction loops, and vague openers—to help diagnose workflow issues.

Instructions

List friction patterns that recur across sessions (repeated file reads, failing commands, correction loops, vague openers, tool-call explosions).

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

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/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden; "List" strongly implies a non-mutating read, and the enumerated pattern types give useful interpretive context. However, it says nothing about scope of access, cost of scanning history, or whether results are ranked, leaving real behavioral gaps for an unannotated tool.

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?

A single front-loaded sentence: verb, resource, scope, then a tight parenthetical of concrete examples. Nothing is padded and nothing needs reordering.

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

Completeness2/5

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

For a four-parameter tool with zero schema description coverage and no annotations, the definition is too thin. An output schema exists so return values needn't be explained, but the agent is left guessing what project, sources, days_back, and min_sessions actually do.

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% and the description never mentions any of the four parameters. "Recur across sessions" faintly gestures at min_sessions, but project scoping, sources, and the days_back window are entirely undocumented, so the description fails to compensate for the schema gap.

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?

Uses a specific verb ("List") with a named resource ("friction patterns") and a scope qualifier ("recur across sessions"), then enumerates five concrete pattern categories so the agent knows exactly what kind of output to expect. It does not differentiate itself from siblings like analyze_sessions or suggest_rules, which is the only thing keeping it off 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 Guidelines2/5

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

There is no explicit guidance on when to reach for this tool versus analyze_sessions, score_sessions, or suggest_rules. The phrase "recur across sessions" implies a diagnostic/retrospective use case, but the agent must infer that, and no exclusions or prerequisites are stated.

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