Skip to main content
Glama
Sign In
xgmem

xgmem

by meetdhanani17
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

search_nodes

Search a project's knowledge graph using entity names, types, and observation content to retrieve matching nodes.

Instructions

Search for nodes in a specific project's knowledge graph based on a query

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

Input Schema

NameRequiredDescriptionDefault
projectIdYesThe project identifier
queryYesThe search query to match against entity names, types, and observation content

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It states the search matches against entity names, types, and observation content, but omits details like whether results are paginated, what is returned (IDs vs full objects), or if the operation is read-only.

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?

The description is a single sentence of 14 words, concise and to the point. However, it could be slightly more informative without adding length.

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

Completeness2/5

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

The tool has no output schema, so the description should clarify what is returned (e.g., list of nodes with certain fields). It only says 'search for nodes', leaving the return format and limitations unclear. For a search tool, pagination and result ordering are also 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 description coverage is 100%, and the description does not add meaning beyond the schema's property descriptions. The tool description only says 'based on a query', which is already implied by the schema. Baseline 3 is 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?

The description clearly states the tool searches for nodes in a project's knowledge graph based on a query, using a specific verb and resource. It distinguishes from siblings like search_all_projects (which searches all projects) and read_graph (which reads the whole graph).

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 description implies usage for searching within a specific project, but lacks explicit guidance on when to use this tool versus alternatives (e.g., search_all_projects). No exclusions or prerequisites are mentioned.

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