SINT Protocol

sint__recall_memory

Search memory bank entries using query strings to retrieve matching data in JSON format, enabling efficient information recall within security protocols.

Instructions

Search the memory bank for entries matching a query string. Returns matching entries as JSON.

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

Input Schema

Name	Required	Description	Default
`query`	Yes	Search query to match against memory entries
`limit`	No	Maximum number of results to return (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 16, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the return format ('as JSON') but lacks details on permissions, rate limits, error handling, or whether the search is case-sensitive/fuzzy. For a search tool with zero annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence that front-loads the core action and outcome without unnecessary words. Every part of the sentence contributes directly to understanding the tool's function, making it optimally concise.

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

Completeness3/5

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

Given the tool's moderate complexity (search operation with 2 parameters), no annotations, and no output schema, the description is minimally adequate. It covers the basic purpose and return format but lacks details on search behavior, result structure, or error cases, which could hinder effective use by an agent.

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?

The schema description coverage is 100%, with clear descriptions for both parameters ('query' and 'limit'). The description adds no additional parameter semantics beyond what the schema provides, such as search syntax or matching criteria, so it meets the baseline for high schema coverage.

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 clearly states the specific action ('Search'), the target resource ('memory bank'), and the outcome ('Returns matching entries as JSON'). It distinguishes itself from siblings like 'store_memory' by focusing on retrieval rather than storage, making the purpose immediately understandable.

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?

The description provides no guidance on when to use this tool versus alternatives. While it implies usage for searching memory entries, it doesn't mention when not to use it or refer to sibling tools like 'store_memory' for related operations, leaving the agent without contextual usage cues.

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