Skip to main content
Glama
Sign In
Soul

Soul

by choihyunsus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

n2_entity_search

Search entities by keyword or type to retrieve matching records and attributes for agent memory and context.

Instructions

Search entities by keyword or type. Returns matching entities with attributes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "n2_entity_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoFilter by type: person, hardware, project, concept, place, service
queryNoSearch keyword

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv9.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden; "Search" implies retrieval rather than mutation, and "Returns matching entities with attributes" usefully describes the result at a high level. It does not disclose matching semantics, result ordering or limits, pagination, empty-result behavior, or any access requirements.

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 front-load the operation and then state the returned content. There is no filler or redundant wording, and the brevity is appropriate for a simple two-parameter search tool.

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?

Together with the fully described schema, the description is minimally sufficient to make a basic call and anticipate entity results. Because there is no output schema or annotation support, the absence of result-shape detail, search behavior, result limits, and sibling-selection guidance leaves noticeable gaps.

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 description coverage is 100%, including the supported entity types, so the baseline applies. The description's "by keyword or type" restates the schema's roles without adding details about case sensitivity, partial matching, combining filters, or omitted-filter behavior.

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?

The description clearly states the action and resource: "Search entities by keyword or type." It also identifies the result as matching entities with attributes, but it does not explicitly differentiate this tool from siblings such as n2_context_search or n2_kv_search.

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?

Keyword and type searching provide an implied use case, so an agent can understand the basic reason to invoke it. There is no explicit guidance on when to prefer it over other search tools, whether filters can be combined, or what to do when neither parameter is supplied.

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