Skip to main content
Glama
Sign In
borer

borer

by imjustprism
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

find_function_by_string

Read-only

Locate functions whose strings contain a case-insensitive text match, returning paged results with a numbered string legend.

Instructions

Find the functions whose strings contain a text, case-insensitively: a numbered string legend, then entry name: 1 2 rows, paged. Not for one function's strings (use function_strings).

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": {
      "filter": "<filter>"
    },
    "name": "find_function_by_string"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows and legend strings (default 50, max 300).
filterYesCase-insensitive substring of the referenced string.
offsetNoFunction rows to skip first (paging).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.5/5.0
Behavior4/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 useful behavioral context: case-insensitive matching, paged output, and the shape of the returned string legend and function rows.

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 description is a single dense sentence plus one routing sentence, with the core action front-loaded. Every clause contributes either purpose, output shape, or disambiguation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, but the description explains the return format and paging behavior. Combined with full parameter schema coverage and annotations covering read-only status, this is sufficient for an agent to invoke the tool correctly.

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 three parameters are already documented in the schema. The description's mentions of case-insensitivity and paging are mildly reinforcing but largely redundant with the schema's own parameter descriptions.

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 verb and resource: find functions whose strings contain a text, case-insensitively. It also distinguishes the tool from sibling `function_strings` and gives a compact indication of its output shape.

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 what the tool is not for — one function's strings — and names the correct alternative, `function_strings`. This directly resolves the most likely sibling ambiguity an agent would face.

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