Skip to main content
Glama
lorenzo-cambiaghi

lynx-mcp

by lorenzo-cambiaghi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

feedback

Report a query failure before giving up. Logs your goal, tried tools, and stuck point locally to help refine the index's sources and filters.

Instructions

Report that the index could not answer you, before giving up. Appended to a local log (never uploaded) so the index owner can tune sources and filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stuckYesWhere exactly you got stuck.
triedYesTools and queries you already tried.
trying_to_doYesWhat you were trying to find or answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.9.0
    • changedInput schema / properties / stuck / description
      Previous value: -"Where exactly you got blocked, or what was missing."New value: +"Where exactly you got stuck."
    • removedInput schema / properties / stuck / title
      Removed value: -"Stuck"
    • changedInput schema / properties / tried / description
      Previous value: -"Which tools and queries you already tried."New value: +"Tools and queries you already tried."
    • removedInput schema / properties / tried / title
      Removed value: -"Tried"
    • removedInput schema / properties / trying_to_do / title
      Removed value: -"Trying To Do"
    • removedInput schema / title
      Removed value: -"_feedbackArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "_feedbackOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.5.1

TDQS

A4.5/5.0
Behavior5/5

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

With all annotation hints false, the description carries the full burden and does so well: it discloses the write side effect (appended), the local persistence (local log), the privacy guarantee (never uploaded), and the downstream purpose (owner tunes sources and filters). This exceeds what the annotations provide.

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 tightly written sentences: the first states the core action and timing, the second explains where the data goes and why it matters. No filler or redundant restatement.

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?

For a simple 3-parameter feedback tool with full schema coverage and no output schema, the description provides everything needed: when to call it, what it does, its storage behavior, and its purpose. Nothing critical is missing.

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 description coverage is 100%, so each parameter is already documented. The tool description adds no additional parameter detail, but the baseline of 3 applies because the schema fully covers semantics.

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 states a specific action: report when the index could not answer. It identifies the resource (local log) and distinguishes itself from sibling index-querying tools by marking feedback as a fallback after failed lookups.

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

Usage Guidelines4/5

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

It clearly signals when to use: when the index could not answer, before giving up. It does not explicitly enumerate excluded cases or name alternatives, but the condition and timing are clear enough for an agent to route to it correctly.

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

Deploy Server

Other Tools