Skip to main content
Glama
Sign In
linklore

linklore

Official
by linklore
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

doc_map

Get a structured overview of the entire document link network, revealing how documents are connected and supporting quick analysis of relationships.

Instructions

[read-only] doc_map(oneline) — overview of the full doc link network.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "doc_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
helpNo
onelineNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits. It only states read-only nature, lacking details on side effects, permissions, or output behavior. This is insufficient for a tool with no annotation safety net.

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 very concise at one line, front-loading the read-only hint. However, it sacrifices necessary parameter explanations, making it too brief for full understanding.

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 absence of parameter descriptions in the schema and no annotations, the description fails to provide complete context. The output schema exists but isn't leveraged in the description. The tool's role among 23 siblings requires more detail.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain the 'help' or 'oneline' parameters beyond mentioning 'oneline' in parentheses. No clarity on their effects or valid values is given.

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 clearly states the tool is for an 'overview of the full doc link network' with a verb-like 'doc_map' and indicates it is read-only. However, it does not explicitly differentiate from sibling tools like doc_flow or doc_rollup.

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 '[read-only]' prefix implies safe usage for reading, but there is no guidance on when to use this tool versus alternatives such as doc_flow or doc_rollup. No exclusions are mentioned.

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