Skip to main content
Glama

krusch_fs_locate

Read-onlyIdempotent

Locate files by glob pattern and metadata filters—category and minimum size—without reading full contents, enabling agents to identify workspace files for follow-up actions.

Instructions

Fast file metadata and glob lookup without reading full file contents.

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

Input Schema

NameRequiredDescriptionDefault
patternNo*
categoryNoall
min_size_bytesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful context that the call returns metadata rather than file bodies and is fast, but says nothing about result fields, result caps, or behavior on invalid globs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the key constraint (metadata only, no contents) is stated immediately. It is efficient but so terse that brevity shades into under-specification.

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?

With three undocumented parameters, no output schema, and no annotation detail beyond hints, the definition leaves too much unresolved for an agent to call it confidently. It should at minimum describe what pattern matching supports and what category values exist.

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?

Schema description coverage is 0%, so the description must carry the parameter burden. 'Glob lookup' loosely maps to pattern, but category and min_size_bytes are completely undocumented and are likely to be misused (e.g., an agent guessing valid category values).

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 description states a specific resource and operation: file metadata and glob-pattern lookup, contrasted against reading the file itself. That implicitly separates it from read-oriented siblings such as krusch_fs_read_page, though it never names any sibling outright.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not guidance and no alternatives are named, so an agent must infer that this is the cheap pre-step before reading or searching. The phrase 'without reading full file contents' only faintly hints at that selection rule.

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