Skip to main content
Glama

find_entity

Search the knowledge graph for entities by partial name or alias, case-insensitively, and optionally filter results by type such as person, organization, domain, topic, project, or source.

Instructions

Search the graph's entities by part of a name or alias, ignoring case. type optionally limits the result to person, organization, domain, topic, project or source.

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": {
      "query": "<query>"
    },
    "name": "find_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden and delivers only the matching semantics (case-insensitive partial match on names/aliases). It says nothing about result capping, ordering/ranking, pagination, or whether multiple types may be supplied, all of which matter for a search 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 compact sentences, front-loaded with the core search behavior and followed by the optional filter. No filler or restatement of the tool name.

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?

For a two-parameter lookup tool with an output schema documenting returns, the description covers both parameters and the matching rule sufficiently to call it correctly. Result limits and ranking behavior are the only meaningful gaps.

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?

Schema coverage is 0%, so the description must supply parameter meaning, and it does: it enumerates the allowed 'type' values (person, organization, domain, topic, project, source), which the schema leaves as an unconstrained string, and explains that 'query' matches part of a name or alias ignoring case. It still omits whether 'type' accepts multiple values or what happens with an unrecognized type.

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

Purpose4/5

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

Names a specific verb ('search') and resource ('graph's entities') plus the matching rule (substring of name or alias, case-insensitive), which is far more informative than the bare name. It does not explicitly distinguish itself from near-neighbors like search_brain or query_notes, so it falls short of a 5.

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 substring/alias matching rule implicitly signals that this is for partial or fuzzy entity lookup, but there is no explicit when-to-use or when-not-to-use guidance and no named alternatives such as search_brain or related_notes. The agent must infer selection criteria.

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