Skip to main content
Glama
Sign In
agent-nexus

agent-nexus

by dugubuyan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

push_document

Push a document version to the exchange center for coordinating updates across heterogeneous LLM code agents.

Instructions

Push a new document version to the exchange center.

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>",
      "content": "<content>"
    },
    "name": "push_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes
doc_idYes
contentYes
metadataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are present, and the description provides no behavioral details such as idempotency, side effects, required permissions, or error behavior. For a mutation tool, this is insufficient.

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 a single sentence, which is concise but at the expense of essential information. It could be expanded slightly to include parameter hints or usage context without losing brevity.

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 no output schema, no annotations, and 4 parameters (3 required) with no documentation, the description fails to provide enough context for correct tool usage. Critical details about input and behavior are missing.

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 coverage is 0%, and the description does not explain any parameters (project_id, doc_id, content, metadata). The agent receives no hints about format, constraints, or expected values beyond schema names.

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 action and resource: 'Push a new document version to the exchange center.' It distinguishes from siblings like 'patch_document' or 'get_document' by emphasizing a new version push.

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 specify when to use this tool versus alternatives like 'publish_draft' or 'patch_document', nor does it mention prerequisites or contexts.

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