Ontonym

Semantic search

semantic_search

Read-onlyIdempotent

Search a graph's classes and objects — meaning AND keywords.

Two rankers run and their results are fused: a vector leg that matches by
meaning (finds the paraphrase) and a keyword leg that matches the literal
words (finds the rare token a vector smooths away — an error code, a
surname, a part number). Each hit carries `via` saying which legs found
it; a hit both agreed on is a stronger answer than one matched on
keywords alone. Ties break toward the NEWER row.

Because the keyword leg needs no index, search still answers on a graph
that was never embedded — with a `note` saying the semantic half was
unavailable. `memory` is the graph's slug from list_my_memories. `kind` =
'class' | 'object' | omit. Check `status` and defer on 'unapproved'.

`expand=1` inlines each top object hit's FIRST RING — properties plus
relationship groups with counts and member previews — so you learn what a
hit is and what it touches without a get_object per hit. Prefer expand=1
whenever you intend to follow relationships; for reach beyond one ring,
use get_paths instead of hopping get_object calls.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	No
`query`	Yes
`top_k`	No
`expand`	No
`memory`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 11, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds substantial behavior: two rankers fused, the `via` field indicating which legs matched, tie-breaking toward the NEWER row, and graceful degradation with a `note` when the graph was never embedded.

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 purpose, then mechanisms, then parameters, then routing guidance — a logical order. It is dense and long, and the expand paragraph could be tightened, but nearly every sentence carries actionable information.

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?

With an output schema present, return-value details need not be explained, and the description still covers fallback behavior, status deferral, and expand semantics. An agent has everything needed to call it correctly and to route to siblings when appropriate.

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 carry the load, and it explains three of five parameters well (memory = graph slug from list_my_memories, kind = 'class'|'object'|omit, expand=1 = inline first ring with counts and previews). top_k is left unexplained and query is only implicit, so it falls just short of fully compensating.

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 ('Search a graph's classes and objects') with explicit scope ('meaning AND keywords'). It distinguishes itself from retrieval siblings like get_object, get_paths, and list_objects by defining the hybrid vector+keyword fusion it performs.

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?

Gives explicit routing: prefer expand=1 when you intend to follow relationships, use get_paths for reach beyond one ring instead of hopping get_object calls, and check `status` and defer on 'unapproved'. Alternatives are named with the conditions that select them.

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

All Ontonym tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?