Skip to main content
Glama
aplaceforallmystuff

MCP Pickaxe Server

by aplaceforallmystuff
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

doc_connect

Link documents to AI agents by adding them to the agent's knowledge base for enhanced information access and processing.

Instructions

Connect/link a document to a Pickaxe agent, adding it to the agent's knowledge base.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
studioNoStudio name to use. Available: STAGING, MAIN, DEV, PRODUCTION. Default: PRODUCTION
documentIdYesThe document ID to connect
pickaxeIdYesThe Pickaxe agent ID to connect the document to

Implementation Reference

  • src/index.ts:493-499 (handler)
    The handler logic for the 'doc_connect' tool. It performs a POST request to the Pickaxe API '/studio/document/connect' endpoint with the required documentId and pickaxeId parameters, and returns the JSON-formatted response.
    case "doc_connect": {
  const result = await pickaxeRequest("/studio/document/connect", "POST", {
    documentId: args.documentId,
    pickaxeId: args.pickaxeId,
  }, studio);
  return JSON.stringify(result, null, 2);
}
  • src/index.ts:175-189 (schema)
    Input schema for the 'doc_connect' tool defining the expected parameters: optional 'studio', required 'documentId' and 'pickaxeId'.
    inputSchema: {
  type: "object",
  properties: {
    studio: studioParam,
    documentId: {
      type: "string",
      description: "The document ID to connect",
    },
    pickaxeId: {
      type: "string",
      description: "The Pickaxe agent ID to connect the document to",
    },
  },
  required: ["documentId", "pickaxeId"],
},
  • src/index.ts:172-190 (registration)
    Registration of the 'doc_connect' tool in the tools array, including name, description, and input schema. This array is used by the MCP server to list available tools.
    {
  name: "doc_connect",
  description: "Connect/link a document to a Pickaxe agent, adding it to the agent's knowledge base.",
  inputSchema: {
    type: "object",
    properties: {
      studio: studioParam,
      documentId: {
        type: "string",
        description: "The document ID to connect",
      },
      pickaxeId: {
        type: "string",
        description: "The Pickaxe agent ID to connect the document to",
      },
    },
    required: ["documentId", "pickaxeId"],
  },
},

Tool Definition Quality

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states this is a mutation operation ('connect/link'), implying it modifies data, but does not disclose behavioral traits such as required permissions, whether the connection is reversible, error handling, or rate limits. The description adds minimal context beyond the basic action.

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 that front-loads the core action and purpose without unnecessary words. Every part earns its place by specifying the action, resource, target, and outcome, making it highly concise and well-structured.

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

Completeness3/5

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

Given the tool's complexity (mutation with 3 parameters), no annotations, and no output schema, the description is minimally adequate. It covers the basic purpose but lacks details on behavior, output, or error handling, leaving gaps that could hinder an agent's ability to use it correctly in all contexts.

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 (studio, documentId, pickaxeId) with descriptions and defaults. The description does not add any meaning beyond what the schema provides, such as explaining parameter interactions or constraints, so it meets the baseline for high coverage.

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 specific action ('connect/link'), resource ('document'), and target ('Pickaxe agent'), distinguishing it from siblings like doc_disconnect (opposite action) and doc_create/delete (different document operations). It explicitly mentions adding to the agent's knowledge base, which clarifies the purpose beyond just linking.

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 description implies usage by specifying the action and target, but does not explicitly state when to use this tool versus alternatives like doc_disconnect or prerequisites. It mentions adding to a knowledge base, which provides some context, but lacks explicit guidance on scenarios or exclusions.

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/aplaceforallmystuff/mcp-pickaxe'

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