Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

search_code

Read-only

Search workspace source files for literal text and return matching lines with line numbers, bounded results, and total bytes.

Instructions

Search text in workspace source files, with line numbers, bounded results and total bytes.

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": {
      "query": "<query>"
    },
    "name": "search_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
globNoOptional glob filter, e.g. **/*.js**/*
limitNoMaximum matches 1..150
queryYesLiteral search text
directoryNoRelative directory.
caseSensitiveNoCase-sensitive search

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that results are bounded and that total bytes and line numbers are returned, but says nothing about truncation behavior, binary/large file handling, or ignore rules – meaningful gaps for a search tool in a real workspace.

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. It could be slightly stronger by front-loading the literal-text nature of the query, but nothing is wasted.

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?

With only one required parameter, a fully documented schema, and no output schema, the description covers the essentials and even sketches the return shape (line numbers, total bytes). Minor incompleteness remains around result ordering and truncation semantics.

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 all five parameters (query, glob, limit, directory, caseSensitive) are already documented in the schema. The description's 'bounded results' hints at limit but adds no syntax or format detail beyond what the schema states. Baseline 3 applies.

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?

States a specific verb and resource: search text in workspace source files. It also previews result shape (line numbers, bounded results, total bytes), which distinguishes it from name-based siblings like glob_files, though no sibling is named 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 by 'search text in workspace source files' – an agent can infer this is for content lookup rather than path listing. However, there is no explicit when-to-use/when-not guidance and no mention of when to prefer read_file or glob_files instead.

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