Skip to main content
Glama
susheel

Synapse MCP Server

get_entity_children

Retrieve child entities within a container entity in Synapse, such as datasets, projects, folders, files, or tables, by providing the container's entity ID.

Instructions

Get child entities of a container entity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entity_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function implementing the get_entity_children tool. Validates the entity ID, retrieves the entity type, and fetches children using project or folder specific operations.
    def get_entity_children(entity_id: str, ctx: Context) -> List[Dict[str, Any]]:
        """List children for Synapse container entities (projects or folders)."""
        if not validate_synapse_id(entity_id):
            return [{"error": f"Invalid Synapse ID: {entity_id}"}]
    
        try:
            entity_ops = get_entity_operations(ctx)
            entity = entity_ops["base"].get_entity_by_id(entity_id)
            entity_type = entity.get("type", "").lower()
    
            if entity_type == "project":
                return entity_ops["project"].get_project_children(entity_id)
            if entity_type == "folder":
                return entity_ops["folder"].get_folder_children(entity_id)
            return [{"error": f"Entity {entity_id} is not a container entity"}]
        except ConnectionAuthError as exc:
            return [{"error": f"Authentication required: {exc}", "entity_id": entity_id}]
        except Exception as exc:  # pragma: no cover - defensive path
            return [{"error": str(exc), "entity_id": entity_id}]
  • Defines the input/output schema and metadata for the tool via the @mcp.tool decorator, including title, description, and operational annotations.
    @mcp.tool(
        title="List Entity Children",
        description="List children for Synapse container entities (projects or folders).",
        annotations={
            "readOnlyHint": True,
            "idempotentHint": True,
            "destructiveHint": False,
            "openWorldHint": True,
        },
    )
  • Registers the tool by importing it from tools.py into the package __init__.py, making it available publicly.
        get_entity,
        get_entity_annotations,
        get_entity_children,
        search_synapse,
    )
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Get') but does not reveal whether this is a read-only operation, if it requires specific permissions, what the output format is, or any rate limits. This leaves significant gaps for an agent to understand the tool's behavior.

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, clear sentence with no wasted words. It is appropriately sized and front-loaded, efficiently conveying the core purpose without unnecessary elaboration.

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 low complexity (1 parameter) and the presence of an output schema, the description is minimally adequate. However, with no annotations and sibling tools present, it lacks context on usage and behavioral traits, making it incomplete for optimal agent decision-making.

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 input schema has 1 parameter with 0% description coverage, so the description must compensate. It clarifies that 'entity_id' refers to a 'container entity', adding meaning beyond the schema's minimal 'Entity Id' title. This is sufficient for the single parameter, though it could be more detailed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the verb ('Get') and resource ('child entities of a container entity'), which clarifies the basic purpose. However, it does not distinguish this tool from sibling tools like 'get_entity' or 'query_entities', leaving ambiguity about when to use this specific tool versus others for retrieving entity-related data.

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. With sibling tools such as 'get_entity', 'query_entities', and 'search_entities' available, there is no indication of context, prerequisites, or exclusions to help an agent choose appropriately.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/susheel/synapse-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server