Skip to main content
Glama
server-noonien

server-noonien

Official

Find Nodes

find_nodes
Read-onlyIdempotent

Search graph entities by multiple words with prefix matching and ranked results, so multi-word or variant-spelling queries return relevant nodes instead of literal-substring misses.

Instructions

Search the graph the way a query is written, not as a literal string: every word must match, a word matches the beginning of a longer one, and the best matches come first. Use it instead of search_nodes when the query is more than one word, or when a word may be spelled differently — ports for port. search_nodes is the literal-substring search and stays for exactly that. A word that matches nothing makes the result empty rather than failing the call.

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_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoThe most entities to return; omit for all of them
queryYesThe words to look for
offsetNoHow many ranked results to skip before the page; omit for none
entityTypeNoKeep only entities of exactly this type; omit to match every type

Output Schema

NameRequiredDescriptionDefault
entitiesYes
relationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), the description discloses non-obvious semantics: all words must match (implicit AND), prefix matching against longer words, ranked output with best first, and that a no-match query returns an empty result rather than an error. That last point in particular is behavior an agent could not infer from annotations or schema.

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 matching model before the sibling comparison, which is the right order. It is slightly redundant in restating that search_nodes is the literal-substring search right after already saying so, but every sentence otherwise carries information.

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?

With an output schema present, return values need no explanation, and the description covers matching rules, ordering, and failure behavior. What is left implicit is which entity fields are searched (names vs. observations) and how entityType interacts with ranking, which would matter for precise querying.

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 100%, so limit/offset/entityType are already documented and baseline would be 3. The description nevertheless adds real meaning to the query parameter — how words are matched, how synonyms/spellings are handled, and what happens on no match — which goes past the schema's terse 'The words to look for'.

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 states a specific action and resource — searching the graph with token-based matching rather than literal substrings — and immediately contrasts it with the sibling search_nodes. An agent can tell the two apart without opening either 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?

Explicit routing rules are given: use this when the query is more than one word or when a word may be spelled differently ('ports for port'), and search_nodes 'stays for exactly' the literal-substring case. Both the when and the when-not are stated.

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