Skip to main content
Glama
lorenzo-cambiaghi

lynx-mcp

by lorenzo-cambiaghi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

update_source_index

Idempotent

Force a full rebuild of a source's index after a large merge or drift warning. Use it to restore search results when the watcher's automatic index is out of sync.

Instructions

Force a full rebuild of a source's index. Expensive and blocking; the watcher keeps the index current, so use it only after a big merge or a drift warning.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceNoRebuild even without new git commits.
sourceYesSource to rebuild.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.9.0
    • changedInput schema / properties / force / description
      Previous value: -"If true, rebuild even when no new git commits are detected."New value: +"Rebuild even without new git commits."
    • removedInput schema / properties / force / title
      Removed value: -"Force"
    • changedInput schema / properties / source / description
      Previous value: -"Name of the source to rebuild (see `list_sources`)."New value: +"Source to rebuild."
    • removedInput schema / properties / source / title
      Removed value: -"Source"
    • removedInput schema / title
      Removed value: -"update_source_indexArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "update_source_indexOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.5.1

TDQS

A4.4/5.0
Behavior4/5

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

The description warns that the operation is 'expensive and blocking,' which goes beyond the annotations. It also clarifies the trigger condition. It does not contradict the annotations, and the annotations already cover the safety profile.

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 entire description is one focused sentence that front-loads the core purpose, then adds cost and usage guidance. No filler or repetition of schema details.

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 two-parameter tool with clear annotations, the description provides enough to select and invoke the tool correctly. It covers purpose, cost, and trigger conditions; the only minor omission is an explicit statement about the return value, but that is not critical for this operation.

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%, so the input schema documents both parameters fully. The description adds contextual meaning around rebuilding and when force is relevant, but it does not add significant parameter-level detail beyond the schema.

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 and resource: 'Force a full rebuild of a source's index.' This clearly distinguishes the tool from read-only siblings like list_sources and search, and from analysis tools like find_usages and impact.

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

Usage Guidelines5/5

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

It explicitly says when to use the tool: 'use it only after a big merge or a drift warning.' It also explains the default state—'the watcher keeps the index current'—which tells the agent not to call this routinely.

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