Skip to main content
Glama

trip2g

by io.github.trip2g
OverviewDiscussionsAdmin

federated_similar

Find remote notes similar to a known note reference inside a connected knowledge base. Preferred: path (a federated_search result's note_path field).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pidNoNon-negative integer (uint64) remote note id, copied verbatim from a federated_search result's note_id field. Prefer path
hrefNoString remote note href, copied verbatim from a federated_search result's href field
pathNoString remote note path, copied verbatim from a federated_search result's note_path field
kb_idYesTarget knowledge base id; nested bases use '/' (e.g. "philosophers/nietzsche" routes through the 'philosophers' peer, recursively). Federation nests up to 3 levels deep (kb_id path segments); a deeper path is rejected.
limitNoMax number of results
note_idNoSame remote note id as pid, but as a STRING (uint64) — stringify the federated_search result's note_id field. Prefer path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations, but description adequately conveys it is a read-only similarity operation on remote notes. Does not detail algorithm or side effects, but suffices for a straightforward tool.

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?

One sentence with a clarifying fragment, no unnecessary words. Action is front-loaded.

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?

Lacks mention of return format or behavior for multiple parameters provided. Sufficient for basic understanding but could elaborate on expected output and edge cases.

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 covers parameter descriptions (100% coverage). Description adds value by specifying preference for 'path' and instructing to copy from federated_search result fields, aiding parameter selection.

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?

Description clearly states verb 'Find... similar to a known note reference' and specifies resource 'remote notes' within a 'connected knowledge base'. It distinguishes itself from sibling 'similar' (local) and 'federated_search' (search).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implicitly suggests using 'path' from federated_search results, but does not explicitly state when to use this tool vs alternatives like 'similar' or conditions to avoid.

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

All trip2g toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources