Skip to main content
Glama
Sign In
DocGraph

DocGraph

by carrilloapps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_related

Fetch related documents for a given document ID from the indexed knowledge graph. Optionally limit results or query a different project.

Instructions

Get related documents

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": {
      "documentId": "<documentId>"
    },
    "name": "get_related"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
documentIdYes
projectPathNoAbsolute path to the indexed project (defaults to the running server’s project root). Use it to query a different project in the same session./app

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations provided, the description bears full responsibility for behavioral transparency. It only states 'Get related documents' without explaining the underlying relatedness logic, performance implications, or whether any side effects occur.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (4 words), but this brevity comes at the expense of informativeness. While it is not verbose, it does not earn its place by providing sufficient detail.

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?

Given the presence of three parameters, no output schema, and no annotations, the description is far from complete. It lacks critical context such as the definition of 'related', how the 'limit' parameter affects results, and any expected output format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% (only 'projectPath' has a description). The tool description adds no additional meaning for parameters 'documentId' and 'limit', leaving the agent uninformed about what 'limit' controls or what 'documentId' refers to.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get related documents' clearly specifies the action (get) and the resource (related documents), making the tool's purpose reasonably clear. However, it does not differentiate from sibling tools like 'get_document_graph' which might also retrieve related documents.

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

Usage Guidelines2/5

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

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives such as 'search' or 'explore', nor does it specify any prerequisites or constraints.

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