Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

kg_find_entity

Read-onlyIdempotent

Find an entity by name in the Knowledge Graph.

USE WHEN user mentions a person, project, company by name and you need:

  • To resolve a name to entity_id for subsequent queries

  • 'Кто работает над X?' → find X first

  • 'Расскажи про Y' → find Y first

RETURNS entity_id for use in kg.get_relationships or kg.explore. ALWAYS use this as the FIRST step in KG query chains.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesEntity name to search for. Can be in any language (Russian, English, etc.) - transliteration is automatic.
limitNoMaximum results to return (1-10). Default: 5
entity_typeNoFilter by entity type: - 'person': People, contacts - 'project': Projects, tasks - 'organization': Companies, teams - 'event': Meetings, deadlines - 'topic': Discussion topics - 'location': Places, addresses - 'document': Files, documents OMIT to include all entity types.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  2. Added
  3. Removed
  4. Changed2 schema fields changed
    • changedInput schema / properties / entity_type / description
      Previous value: -"Filter by entity type:\n- 'person': People, contacts\n- 'project': Projects, tasks\n- 'organization': Companies, teams\n- 'event': Meetings, deadlines\n- 'topic': Discussion topics\n- 'location': Places, addresses\n- 'document': Files, documents\n- 'workspace': User's own facts (my/our company)\nOMIT to include all entity types."New value: +"Filter by entity type:\n- 'person': People, contacts\n- 'project': Projects, tasks\n- 'organization': Companies, teams\n- 'event': Meetings, deadlines\n- 'topic': Discussion topics\n- 'location': Places, addresses\n- 'document': Files, documents\nOMIT to include all entity types."
    • changedInput schema / properties / entity_type / enum
      Previous value: -[
-  "person",
-  "project",
-  "organization",
-  "event",
-  "topic",
-  "location",
-  "document",
-  "workspace"
-]New value: +[
+  "person",
+  "project",
+  "organization",
+  "event",
+  "topic",
+  "location",
+  "document"
+]
  5. Changed2 schema fields changed
    • changedInput schema / properties / entity_type / description
      Previous value: -"Filter by entity type:\n- 'person': People, contacts\n- 'project': Projects, tasks\n- 'organization': Companies, teams\n- 'event': Meetings, deadlines\n- 'topic': Discussion topics\n- 'workspace': User's own facts (my/our company)\nOMIT to include all entity types."New value: +"Filter by entity type:\n- 'person': People, contacts\n- 'project': Projects, tasks\n- 'organization': Companies, teams\n- 'event': Meetings, deadlines\n- 'topic': Discussion topics\n- 'location': Places, addresses\n- 'document': Files, documents\n- 'workspace': User's own facts (my/our company)\nOMIT to include all entity types."
    • changedInput schema / properties / entity_type / enum
      Previous value: -[
-  "person",
-  "project",
-  "organization",
-  "event",
-  "topic",
-  "workspace"
-]New value: +[
+  "person",
+  "project",
+  "organization",
+  "event",
+  "topic",
+  "location",
+  "document",
+  "workspace"
+]
  6. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds meaningful behavioral context: it returns entity_id specifically for chaining into kg.get_relationships/kg.explore. It stops short of describing match behavior (ambiguity handling, ranking) or what happens when no entity is found.

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?

Front-loads the core purpose, then uses labeled USE WHEN / RETURNS / ALWAYS sections. Every line earns its place and the downstream-chaining rule is prominent, aiding fast scanning.

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?

No output schema exists, yet the description explicitly states the return value (entity_id) and its intended downstream use. With all four parameters fully documented in the schema and the chaining role explained, an agent has everything needed to invoke it correctly.

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% with full inline descriptions for name, limit, entity_type, and in_workspace, so the schema carries the parameter burden. The description adds no parameter syntax or semantics beyond what the schema already provides, making the baseline of 3 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?

States a specific verb and resource ('Find an entity by name in the Knowledge Graph') and clarifies its role as the entry point to KG query chains. It distinguishes itself from kg.get_relationships and kg.explore by positioning itself as the name-resolution step that precedes them.

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?

Explicit 'USE WHEN' block names the trigger (a named person/project/company) and gives concrete examples including the 'find X first' pattern. It also names the downstream tools and states 'ALWAYS use this as the FIRST step in KG query chains,' leaving little to inference.

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

All dialogbrain toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources