Skip to main content
Glama

knowledge_related

Read-onlyIdempotent

Retrieve semantically related objects from a specified collection using vector search. Provide a source object UUID and collection to find relevant results.

Instructions

Find semantically related objects using near-object vector search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_idYesUUID of the source object
collectionYesCollection the source object belongs to.
limitNoMax related results

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the description adds only the method 'near-object vector search'. No additional behavioral context is provided beyond what annotations cover.

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?

The description is a single sentence of 10 words, front-loaded with the verb and resource. Every word is necessary, and there is no redundancy or waste.

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?

Given the tool's simplicity (3 parameters, 2 required), high schema coverage, and existence of an output schema, the description fully conveys the tool's purpose and behavior. No gaps are apparent.

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?

Input schema has 100% description coverage for all three parameters. The description adds no extra meaning beyond the schema. Baseline score of 3 is appropriate as the schema already documents each parameter.

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 specifies the action 'Find', the resource 'semantically related objects', and the method 'near-object vector search'. It distinguishes from siblings like knowledge_search (text search) and knowledge_query (structured query).

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 finding semantically related objects but provides no explicit guidance on when to use this tool versus alternatives (e.g., knowledge_search, knowledge_query). No when-not or alternative names are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Galbaz1/video-research-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server