Skip to main content
Glama
Sign In

secondbrain

by media.secondbrain
OverviewDiscussionsAdmin

get_entity_details

Read-only

Obtiene el detalle completo de una entidad del knowledge graph por ID.

Retorna: id, canonical_name, type, description, context (texto libre de contexto), aliases (nombres alternativos), relations_cache (relaciones resumidas), occurrence_count (veces mencionada), created_at, updated_at.

Además dos señales calculadas sobre el CONTENIDO asociado, no sobre el nombre:
  similar_by_content   → entidades que hablan de lo mismo. "likely_duplicate: true" marca las
                         que además tienen el nombre parecido: casi siempre es la misma cosa
                         cargada dos veces, y conviene proponer merge_entities.
  suggested_relations  → relaciones que NO están cargadas pero el contenido sugiere, con
                         cuántas veces aparecen juntas y cuántas veces por encima del azar.
                         Para crearlas: add_entity_relation.

wiki_summary es el resumen del artículo del wiki (fresco); para el artículo entero, get_entity_wiki.
occurrence_count = en cuántas fuentes (recaps, docs, notas, tareas) aparece.

Usar cuando necesitas todos los datos de una entidad, incluyendo contexto y aliases, después de encontrar su ID con search_entities.

Input Schema

NameRequiredDescriptionDefault
entity_idYesID de la entidad
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: the meaning of occurrence_count, that wiki_summary is fresh, and that similar_by_content with likely_duplicate=true signals a probable duplicate worth a merge_entities call. It does not discuss auth or rate limits, but with annotations present that gap is minor.

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?

Front-loaded with the purpose, then the return fields, then the computed signals, then usage. Every section is purposeful, though the long return-field enumeration and the nested explanatory indentation make it heavier than a strictly necessary description.

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

Completeness5/5

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

There is no output schema, so the description carries the return-value burden and does so fully: it enumerates the returned fields, explains the two computed signals and what the boolean flags mean, and clarifies wiki_summary vs get_entity_wiki. Nothing needed to interpret the result is missing.

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% and both parameters are documented in the schema itself, including the workspace_id fallback. The description adds nothing beyond 'por ID', so the baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource ('Obtiene el detalle completo de una entidad del knowledge graph por ID') and clearly delimits it against siblings: wiki_summary is only the summary vs get_entity_wiki for the full article. An agent can distinguish this from get_entity_relations, get_entity_wiki and search_entities without opening a schema.

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

Usage Guidelines5/5

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

Explicitly states when to use it ('cuando necesitas todos los datos de una entidad, incluyendo contexto y aliases') and the prerequisite ('después de encontrar su ID con search_entities'). It also names where to go next for related needs (get_entity_wiki, merge_entities, add_entity_relation), so the routing is complete.

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

All secondbrain toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources