Skip to main content
Glama
Sign In
search-docs

search-docs

by otolab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_document

Retrieve document content using either a section ID for a section's full text or a document path for the entire document.

Instructions

文書の内容を取得します。セクションの全文はsectionId、文書全体はpathを指定します。

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": "get_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo文書パス（sectionIdを指定しない場合は必須）
projectNo関連プロジェクト名（未指定時はメインプロジェクト）
sectionIdNoセクションID（検索結果から取得。pathを指定しない場合は必須）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.9.4

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the two retrieval behaviors (section vs whole document) but does not mention any permissions, side effects, or output format. The read-only nature is implied by 'get' but not explicitly stated.

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 two short sentences with no fluff. It front-loads the core purpose and then provides parameter guidance efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity and no output schema, the description adequately covers the main usage and parameter roles. It lacks details on edge cases (e.g., both path and sectionId provided) and return format, but those are not critical for a basic getter tool.

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?

Schema description coverage is 100%, so the schema already documents all three parameters. The description adds a small amount of semantic clarity by explaining what each parameter returns (section full text vs whole document), but this is largely redundant with schema property descriptions.

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 the tool retrieves document content (文書の内容を取得します) and specifies two modes: section full text via sectionId, whole document via path. This distinguishes it from siblings like search and get_outline.

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?

Provides clear guidance on when to use sectionId versus path, which is practical parameter selection. However, it does not explicitly discuss tool-level alternatives or when not to use this tool, though the name and context make its purpose obvious.

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