Skip to main content
Glama
nulab

Backlog MCP Server

get_document

Retrieve document details from Backlog projects using its unique ID to access information and content.

Instructions

Gets information about a document.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
documentIdYesDocument ID

Implementation Reference

  • The handler function that implements the core logic of the 'get_document' tool by retrieving the document using the Backlog client's getDocument method.
    handler: async ({ documentId }) => {
      return backlog.getDocument(documentId);
    },
  • The Zod input schema definition for the 'get_document' tool, specifying the required 'documentId' string parameter.
    const getDocumentSchema = buildToolSchema((t) => ({
      documentId: z
        .string()
        .describe(t('TOOL_GET_DOCUMENT_DOCUMENT_ID', 'Document ID')),
    }));
  • Registration of the 'get_document' tool within the 'document' toolset group by calling its factory function getDocumentTool and adding it to the tools array.
    tools: [
      getDocumentsTool(backlog, helper),
      getDocumentTreeTool(backlog, helper),
      getDocumentTool(backlog, helper),
    ],
  • The factory function that creates and defines the ToolDefinition object for 'get_document', including name, description, schema, and handler.
    export const getDocumentTool = (
      backlog: Backlog,
      { t }: TranslationHelper
    ): ToolDefinition<
      ReturnType<typeof getDocumentSchema>,
      (typeof DocumentItemSchema)['shape']
    > => {
      return {
        name: 'get_document',
        description: t(
          'TOOL_GET_DOCUMENT_DESCRIPTION',
          'Gets information about a document.'
        ),
        schema: z.object(getDocumentSchema(t)),
        outputSchema: DocumentItemSchema,
        importantFields: ['id', 'title', 'createdUser'],
        handler: async ({ documentId }) => {
          return backlog.getDocument(documentId);
        },
      };
    };
Behavior2/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 of behavioral disclosure. It only states the action ('Gets information') without detailing traits like read-only nature, error handling, authentication needs, rate limits, or response format. This is inadequate for a tool with no annotation coverage, as critical behavioral context is missing.

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, efficient sentence with zero wasted words. It is front-loaded with the core action and resource, making it easy to parse quickly. Every part of the sentence earns its place by conveying the essential purpose without redundancy.

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 complexity of a document retrieval tool with no annotations and no output schema, the description is incomplete. It lacks details on what information is returned, error conditions, or behavioral traits, leaving significant gaps for an agent to understand how to use it effectively in context.

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?

The input schema has 100% description coverage, with 'documentId' documented as 'Document ID'. The description adds no additional meaning beyond this, such as format examples or constraints. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description does not compensate but also does not detract.

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

Purpose3/5

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

The description 'Gets information about a document' clearly states the verb ('Gets') and resource ('document'), making the purpose understandable. However, it lacks specificity about what information is retrieved (e.g., metadata, content, permissions) and does not distinguish it from sibling tools like 'get_documents' (plural) or 'get_document_tree', leaving the scope vague.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as needing a valid document ID, or compare it to siblings like 'get_documents' for listing documents or 'get_document_tree' for hierarchical views, leaving the agent without context for selection.

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/nulab/backlog-mcp-server'

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