memkin

List Signals by Entity

list_signals_by_entity

Retrieve decisions, tasks, and knowledge anchored to a specific entity such as a person, project, or tool. Optionally filter by signal type to narrow results.

Instructions

list_signals_by_entity

List all signals anchored to an entity.

When to use: retrieve decisions, tasks, knowledge, etc. for a specific person/project/tool. Returns: signals with type, title, and summary.

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": {
      "entity_slug": "<entity_slug>"
    },
    "name": "list_signals_by_entity"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum signals, default 20.
`entity_slug`	Yes	Entity slug, for example `entities/alice`.
`signal_types`	No	Optional signal type filter.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 13, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It describes the tool as a read operation (list) but does not disclose any behavioral traits such as authentication requirements, rate limits, or side effects. The description is minimal and adequate but lacks depth.

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 extremely concise: two lines of substantive content plus a heading. Every sentence adds value: purpose, usage context, and return format. No wasted words.

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 has 3 parameters (1 required) and no output schema. The description explains it returns signals with type, title, and summary, which is sufficient for basic use. However, it could mention pagination behavior given the limit parameter, and it lacks details on ordering or filtering behavior. Slightly incomplete but acceptable.

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 coverage is 100%, so the schema already documents all three parameters. The description adds no extra meaning beyond the schema; it only mentions returned fields. Baseline of 3 is appropriate since the description does not enhance parameter understanding.

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 tool lists all signals anchored to an entity, with specific verb 'List' and resource 'signals anchored to an entity'. It distinguishes from siblings like search or query by specifying the scoped retrieval for a specific person/project/tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description includes 'When to use: retrieve decisions, tasks, knowledge, etc. for a specific person/project/tool' which gives clear context for appropriate usage. However, it does not explicitly mention when not to use or alternatives, so it lacks exclusions.

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