copilot-studio-friction-index

List friction records

list_frictions

Read-only

Browse the register: compact list of all published friction records, sorted by last-verified date (newest first). Filter by status and/or category.

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

Input Schema

Name	Required	Description	Default
`locale`	No	Output and citation language. English fallback when a current German translation is unavailable.	en
`status`	No	Optional status filter: "open" (problem exists), "mitigated" (reliable workaround), "fixed" (resolved and re-verified), "regressed" (was fixed, is back).
`category`	No	Optional category filter.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 13, 2026

addedInput schema / properties / locale

Added value: +{
+  "default": "en",
+  "description": "Output and citation language. English fallback when a current German translation is unavailable.",
+  "enum": [
+    "en",
+    "de"
+  ],
+  "type": "string"
+}

First observedJul 13, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond the readOnly/openWorld annotations, the description discloses scope ('published' only), projection ('compact list'), and sort order ('newest first by last-verified date'), which materially shape what an agent gets back. It does not mention any result cap or pagination behavior, which is the main remaining gap.

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?

Two sentences, zero filler, and the essential scope/ordering information is front-loaded before the filter clause.

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 read-only list tool with no output schema, the definition covers scope, ordering, and filters adequately. A brief note on result size or truncation would close the last gap.

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?

Schema coverage is 100% and every parameter carries a rich enum description, so the schema already does the heavy lifting for status, category, and locale. The description only restates the status/category filtering at a high level and adds nothing about the locale parameter.

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?

States a specific verb ('browse') and resource ('all published friction records'), plus the ordering ('sorted by last-verified date, newest first'). It does not name or contrast with the sibling search_frictions, so an agent must infer that this is enumeration rather than query-based retrieval.

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?

'Browse the register' plus optional status/category filters implies the enumeration use case, and the filters hint at narrowing. However, there is no explicit guidance on when to prefer search_frictions or get_friction_record over this tool.

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

All copilot-studio-friction-index tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?