Skip to main content
Glama
Sign In
Agent Memory Engine

Agent Memory Engine

by ululazmi18
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

memory_find_by_intent

Search code symbols, files, or exact blocks using natural language, colloquial slang, command habits, or typos to locate relevant references without scanning raw files.

Instructions

Search symbols, files, or exact code blocks using natural human language, Indonesian colloquial slang, command habits, or typos.

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": {
      "terms": "<terms>"
    },
    "name": "memory_find_by_intent"
  }
}

Input Schema

NameRequiredDescriptionDefault
termsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It implies a non-mutating search and clarifies accepted query styles, but it does not discuss matching behavior, result limits, permissions, or other operational traits.

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, front-loaded sentence with no filler. The core action and the accepted query styles are stated efficiently.

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?

The tool is simple, has one required parameter, and includes an output schema, so the description need not explain return values. It conveys enough to attempt a call, though it lacks explicit guidance on when to choose this tool over the siblings.

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 compensate for the single 'terms' parameter. It usefully explains that terms may be natural language, slang, command habits, or typos, but it does not clarify how the array is interpreted or whether multiple terms affect matching.

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 verb, 'Search', and specific resource types: symbols, files, and exact code blocks. It is clear what the tool does, though it does not explicitly differentiate itself from the sibling memory_* tools.

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?

The description implies usage by listing input styles such as natural language, Indonesian slang, command habits, and typos. However, it does not state when to use this tool versus alternatives or when not to use it.

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