Skip to main content
Glama
Sign In
agent-nexus

agent-nexus

by dugubuyan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_document

Retrieve documents from a versioned Markdown store by project and document ID. Optionally specify a version number to access historical content.

Instructions

Retrieve a document (latest or specific version).

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": {
      "project_id": "<project_id>",
      "doc_id": "<doc_id>"
    },
    "name": "get_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes
doc_idYes
versionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It implies read-only retrieval but lacks details about what is returned (e.g., content vs metadata) or any constraints. The version option is mentioned but not explained how it affects behavior.

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

Conciseness4/5

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

The description is very concise at one sentence, with no fluff. However, the extreme brevity omits necessary details, so it balances conciseness and completeness poorly.

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?

For a tool with 3 parameters, no output schema, and no annotations, the description is insufficient. It does not cover return format, error cases, or how version is used, leaving an agent without enough information to invoke the tool correctly.

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?

The input schema has 0% description coverage, and the tool description does not add any meaning beyond parameter names and types. It does not explain the purpose of project_id, doc_id, or the version parameter (e.g., null for latest).

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 states the tool retrieves a document, specifying that it can retrieve the latest or a specific version. This matches a specific verb+resource and distinguishes it from siblings like list_documents and patch_document.

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 like list_documents. There are no exclusions or context about prerequisites or appropriate scenarios.

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