Skip to main content
Glama
jakedx6

Helios-9 MCP Server

by jakedx6

associate_document_with_initiative

Link a document to an initiative by providing the initiative ID and document ID.

Instructions

Link an existing document to an initiative

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
initiative_idYesThe initiative ID to associate the document with
document_idYesThe document ID to associate with the initiative

Implementation Reference

  • The main handler function for associate_document_with_initiative. Validates inputs with Zod (initiative_id and document_id as UUIDs), logs the operation, calls the API client to create the association, and returns a success response.
    export const associateDocumentWithInitiative = requireAuth(async (args: any) => {
      const { initiative_id, document_id } = z.object({
        initiative_id: z.string().uuid(),
        document_id: z.string().uuid()
      }).parse(args)
      
      logger.info('Associating document with initiative', { initiative_id, document_id })
      
      // Call the API to create the association
      const response = await supabaseService.associateDocumentWithInitiative(initiative_id, document_id)
      
      logger.info('Document associated with initiative successfully')
      
      return {
        success: true,
        message: `Document successfully associated with initiative`,
        initiative_id,
        document_id
      }
    })
  • The MCP tool definition (MCPTool object) including the name, description, and input JSON Schema for associate_document_with_initiative. Defines initiative_id and document_id as required UUID strings.
    export const associateDocumentWithInitiativeTool: MCPTool = {
      name: 'associate_document_with_initiative',
      description: 'Link an existing document to an initiative',
      inputSchema: {
        type: 'object',
        properties: {
          initiative_id: {
            type: 'string',
            format: 'uuid',
            description: 'The initiative ID to associate the document with'
          },
          document_id: {
            type: 'string',
            format: 'uuid',
            description: 'The document ID to associate with the initiative'
          }
        },
        required: ['initiative_id', 'document_id']
      }
    }
  • Tool registration: associateDocumentWithInitiativeTool is exported in the initiativeTools object.
    associateDocumentWithInitiativeTool,
  • Handler registration: the associateDocumentWithInitiative handler is mapped to the name 'associate_document_with_initiative' in the initiativeHandlers export object.
    associate_document_with_initiative: associateDocumentWithInitiative,
  • The API client helper method that makes the actual HTTP POST request to /api/mcp/initiatives/{initiativeId}/documents to associate a document with an initiative.
    async associateDocumentWithInitiative(initiativeId: string, documentId: string): Promise<any> {
      const response = await this.request<{ success: boolean }>(`/api/mcp/initiatives/${initiativeId}/documents`, {
        method: 'POST',
        body: JSON.stringify({ document_id: documentId }),
      })
      
      logger.info(`Document ${documentId} associated with initiative ${initiativeId}`)
      return response
    }
Behavior3/5

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

No annotations are provided, so the description must bear the transparency burden. It states the basic action but does not disclose idempotency, error handling, or permission requirements. Acceptable for a simple association but lacks depth.

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?

A single, concise sentence with no extraneous words. Efficiently communicates the core function.

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?

For a simple tool with two parameters and no output schema, the description is largely adequate. It could mention that IDs must correspond to existing entities, but overall complete enough.

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 coverage is 100% with descriptions for both parameters. The description adds no additional meaning beyond repeating the schema's information. Baseline 3 due to 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 uses specific verb 'Link' and identifies both resources (document, initiative). It clearly distinguishes from the sibling tool 'disassociate_document_from_initiative'.

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 context on when to use this tool, prerequisites (e.g., document and initiative must exist), or alternatives. It simply states the action.

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/jakedx6/helios9-MCP-Server'

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