Skip to main content
Glama
Sign In
memory

memory

by harsh-gulhane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

find_by_entity

Retrieve all memories linked to a specific entity type and value, such as a person, service, or account, to trace related notes and context.

Instructions

Find all memories linked to a specific entity (person, service, account, etc.).

Args: entity_type: Type of entity (e.g. "person", "service", "account", "bucket", "ticket") entity_value: Value to search, substring match (e.g. "alice", "billing-api", "prod-db") limit: Maximum results (default: 25, max: 200)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_by_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
entity_typeNo
entity_valueNo

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 discloses some behavioral details: entity_value uses substring matching, and limit has a default of 25 and maximum of 200. However, it omits other relevant traits such as whether the operation is read-only (implied but not stated), error handling, or pagination behavior.

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?

The description is reasonably concise, with a clear opening sentence and structured parameter list. The 'Args:' formatting is slightly verbose but necessary given the schema lacks descriptions, and the content is front-loaded.

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 find tool with three optional parameters, no annotations, and an output schema, the description covers purpose, all parameters, and key behavioral details. A minor gap is not explicitly stating that entity_type and entity_value are optional (though the schema shows defaults).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description fully compensates by explaining all three parameters with examples and constraints: entity_type with example values, entity_value with substring match and examples, and limit with default and maximum.

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 clearly states 'Find all memories linked to a specific entity', specifying the verb (find) and resource (memories linked to an entity). It does not explicitly distinguish itself from sibling tools like search_memory or list_memories, which prevents a 5.

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?

No guidance is given on when to use this tool versus alternatives such as search_memory or list_entities. The description only explains parameters, leaving the agent to infer appropriate usage contexts.

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