Skip to main content
Glama
Sign In
Engram

Engram

by staticroostermedia-arch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

mcp_engram_goal_get_children

List all direct child goals for a given parent to traverse the goal decomposition tree.

Instructions

Return all direct child (sub) goals for a given parent goal. Supports traversing the goal decomposition tree.

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": {
      "parent": "<parent>"
    },
    "name": "mcp_engram_goal_get_children"
  }
}

Input Schema

NameRequiredDescriptionDefault
parentYesParent goal concept name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0-beta.2

TDQS

A4/5.0
Behavior4/5

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

No annotations provided, so description carries burden. Accurately states tool returns children and supports traversal. Lacks details on error handling or empty results, but overall honest and complete for a simple read operation.

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?

Two short sentences pack essential information without filler. Efficient and 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?

Given no output schema and simplicity, description is adequate: explains input, output (children), and purpose (traversal). Minor omission: behavior when parent not found or no children.

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 already describes 'parent' with 'Parent goal concept name'. Description adds no new semantic value beyond implying hierarchical context. With 100% schema coverage, baseline 3 is appropriate.

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?

Description clearly uses specific verb 'return all direct child goals' and resource 'parent goal'. Distinguishes from siblings like goal_list, goal_search, and goal_decompose by focusing on hierarchical traversal.

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?

Implies usage for traversing goal decomposition tree but does not explicitly state when to use vs alternatives like goal_list or goal_decompose. Missing guidance on prerequisites or context.

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