Skip to main content
Glama
Sign In
Mnemograph

Mnemograph

by tm42
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

find_orphans

Identifies entities without any relations, highlighting incomplete data that requires connection, merging, or deletion.

Instructions

Find entities with no relations (likely incomplete). Orphans should be connected, merged into another entity, or deleted.

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_orphans"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It states the tool finds orphans but does not specify whether it is read-only or modifies data, nor does it mention any side effects or permissions needed. This is insufficient transparency.

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 two sentences, directly stating purpose and recommended actions. No extraneous text; every sentence earns its place.

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

Completeness2/5

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

Given no output schema, the description should explain the return value (e.g., list of entity IDs). It does not. The tool is simple but the output format is ambiguous, reducing completeness.

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

Parameters4/5

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

The tool has zero parameters, so by instruction baseline is 4. The description does not need to add parameter information, and it does not hinder 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 finds entities with no relations, using a specific verb ('Find') and resource ('entities with no relations'). It distinguishes from sibling tools like 'get_weak_relations' or 'suggest_relations' which deal with relations but not specifically orphans.

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 for finding incomplete entities and suggests actions (connect, merge, delete), but it does not explicitly state when to use this tool or when to use alternatives. Minimal guidance is provided.

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