Skip to main content
Glama
Sign In
skim-mcp

skim-mcp

by helloderekg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

skim_search

Find lines or anchors containing a search query in a file without reading the entire content.

Instructions

Find which anchors/lines contain query (case-insensitive) without reading the whole file.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "handle": "<handle>",
      "query": "<query>"
    },
    "name": "skim_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
handleYes
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Mentions case-insensitive search and efficiency, but omits details like result format (e.g., line numbers) or max_results behavior.

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?

Single sentence, 10 words, front-loaded with purpose. Every word earns its place.

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?

No output schema, yet description does not indicate what results contain (e.g., matched lines, positions). Missing guidance on interpreting output, essential for a search tool.

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?

With 0% schema description coverage, the description only adds value for 'query' parameter. 'handle' and 'max_results' are not explained, leaving significant gaps.

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?

Clearly states the verb 'find' and the resource 'anchors/lines' with the specific behavior 'case-insensitive' and efficiency 'without reading the whole file'. Distinguishes from sibling tools like skim_open and skim_expand.

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?

Implicitly suggests use for quick searches without reading full file, but lacks explicit when-to-use or when-not-to-use statements. Sibling names provide some context for alternatives.

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