Skip to main content
Glama

attach_file

Attaches a file to a task, note, or comment in Repsona projects. Specify project, model type, and IDs to link files to specific items.

Instructions

指定したファイルをタスクやノートに添付します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesプロジェクトID
modelYesタスク、タスクコメント、ノート、ノートコメント
modelIdYesタスクID、タスクコメントID、ノートID、ノートコメントID
fileIdYesファイルID

Implementation Reference

  • RepsonaAPI.attachFile method - Makes an API PUT request to attach a file to a model (task, task_comment, note, note_comment) in the Repsona project.
    async attachFile(projectId, model, modelId, fileId) {
      return this.makeRequest(`/project/${projectId}/${model}/${modelId}/files/${fileId}`, 'PUT');
    }
  • Tool schema/input definition for 'attach_file' - defines the required parameters: projectId, model (enum: task/task_comment/note/note_comment), modelId, and fileId.
    {
      name: 'attach_file',
      description: '指定したファイルをタスクやノートに添付します',
      inputSchema: {
        type: 'object',
        properties: {
          projectId: { type: 'string', description: 'プロジェクトID' },
          model: { 
            type: 'string', 
            enum: ['task', 'task_comment', 'note', 'note_comment'],
            description: 'タスク、タスクコメント、ノート、ノートコメント' 
          },
          modelId: { type: 'string', description: 'タスクID、タスクコメントID、ノートID、ノートコメントID' },
          fileId: { type: 'string', description: 'ファイルID' },
        },
        required: ['projectId', 'model', 'modelId', 'fileId'],
      },
    },
  • index.js:717-718 (registration)
    Registration of the 'attach_file' tool in the ListToolsRequestSchema handler - defines the tool name, description, and input schema.
    name: 'attach_file',
    description: '指定したファイルをタスクやノートに添付します',
  • Handler for the 'attach_file' tool in the CallToolRequestSchema switch statement - calls repesonaAPI.attachFile with projectId, model, modelId, and fileId, returns a JSON result.
    case 'attach_file':
      const attachResult = await this.repsonaAPI.attachFile(args.projectId, args.model, args.modelId, args.fileId);
      return {
        content: [
          {
            type: 'text',
            text: `ファイルが添付されました: ${JSON.stringify(attachResult, null, 2)}`,
          },
        ],
      };
Behavior2/5

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

With no annotations, the description carries the full burden. It only states the basic action, ignoring behavioral traits like whether the file is required to be already uploaded, if multiple attachments are allowed, or any side effects on existing attachments.

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 a single concise sentence that front-loads the action. It is efficient but could include more detail without harming conciseness.

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?

The description lacks important contextual details such as the return value, success/failure behavior, and the full set of attachment targets (model enum values). For a tool with no output schema and 4 required parameters, this is inadequate.

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%, so each parameter is already described. The description adds no extra meaning or context beyond what the schema provides, justifying the baseline of 3.

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 ('attach') and the target objects ('task or note'), distinguishing it from siblings like detach_file and upload_file. However, it omits that the model parameter also supports 'task_comment' and 'note_comment' as per the schema enum.

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 guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites (e.g., file must exist) or scenarios where detach_file or upload_file would be more appropriate.

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/bellx2/repsona-mcp-server'

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