Skip to main content
Glama
Sign In
agent-mcp

agent-mcp

by uukelele
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Glob

glob
Read-only

Find files by pattern such as '**/*.ts'; hidden files are skipped unless hidden=true, and newest matches are returned first.

Instructions

Find files by glob pattern such as '**/*.ts'. Hidden files are skipped unless hidden=true. Results are newest first.

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": {
      "pattern": "<pattern>"
    },
    "name": "glob"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
limitNo
hiddenNo
patternYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds two genuinely non-obvious behaviors: hidden files are excluded unless hidden=true, and results are returned newest first. It says nothing about truncation at the limit default of 100 or how many results to expect, which matters for a discovery tool.

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?

Three short, front-loaded sentences with zero filler: what it does, a syntax example, then the two behavioral caveats. Nothing is repeated from the schema or annotations.

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 simple read-only file-finding tool with an output schema present, the description covers purpose, default filtering, and ordering, which is enough to call it correctly. The remaining gaps (default search root for path, what happens when limit is hit) are minor but real for a tool with four parameters.

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 0%, so the description must carry parameter meaning; it does so for pattern (glob syntax with an example) and hidden (default exclusion behavior). It leaves path (the search root) and limit (default 100, truncation semantics) entirely undocumented, so compensation is only partial.

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 uses a specific verb and resource ("Find files") and supplies an illustrative glob pattern ('**/*.ts'), which makes the tool's job unambiguous. It implicitly separates itself from the content-searching sibling grep by talking about finding files rather than matching contents, but it never names that sibling explicitly.

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?

Usage is implied rather than stated: an agent can infer this is the tool for locating files by path pattern. There is no explicit guidance on when to prefer it over grep, shell, or read, and no mention of prerequisites such as path scope.

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