V.I.S.O.R.

Overview Schema Source Related Servers Discussions Admin

list_context_feedback

Retrieve explicit retrieval feedback for your workspace, optionally filtering by query similarity to focus on relevant records.

Instructions

    List explicit retrieval feedback for the current workspace.

    When ``query`` is set, only records at or above the lexical similarity
    threshold for that query and intent are returned.

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

Input Schema

Name	Required	Description	Default
`query`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.4.2Nov 3, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral burden; it usefully adds workspace scoping and threshold-based filtering, while "List" implies a read operation. It does not explicitly confirm non-mutation or explain result ordering, pagination, or how the threshold and intent are determined.

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 purpose is front-loaded, followed by a focused explanation of the only optional parameter. Both sentences earn their place, and the length is appropriate for the tool.

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 one-parameter listing tool with an output schema, the purpose, workspace scope, and filtering behavior cover most invocation needs. Clarifying the intent source and similarity threshold would make the filtering behavior fully actionable.

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

Parameters4/5

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

Despite 0% schema description coverage, the description explains that setting query restricts results to records meeting a lexical similarity threshold. The unspecified threshold and unexplained reference to intent leave some ambiguity, but the sole parameter is substantially clearer than the schema alone.

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 verb "List," resource "explicit retrieval feedback," and scope "current workspace" make the operation clear. It does not explain what constitutes retrieval feedback or explicitly distinguish its inspection role from the record, delete, and clear feedback siblings.

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?

The description implies use for inspecting workspace feedback and explains when the optional query affects results. However, it provides no explicit tool-selection guidance, prerequisites, or comparison with related context and feedback tools.

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