Skip to main content
Glama
TAgents

Planning System MCP Server

by TAgents

batch_get_artifacts

Retrieve multiple artifacts simultaneously from a planning system using plan ID and artifact requests to efficiently access structured project data.

Instructions

Get multiple artifacts at once

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
plan_idYesPlan ID
artifact_requestsYesList of artifact requests

Implementation Reference

  • Handler function that processes batch artifact requests by fetching each artifact and its content using apiClient, collecting successes and errors, and returning formatted response.
    if (name === "batch_get_artifacts") {
      const { plan_id, artifact_requests } = args;
      
      const results = [];
      const errors = [];
      
      for (const request of artifact_requests) {
        const { node_id, artifact_id } = request;
        try {
          const artifact = await apiClient.artifacts.getArtifact(plan_id, node_id, artifact_id);
          const content = await apiClient.artifacts.getArtifactContent(plan_id, node_id, artifact_id);
          results.push({
            node_id,
            artifact_id,
            success: true,
            data: { ...artifact, content }
          });
        } catch (error) {
          errors.push({
            node_id,
            artifact_id,
            success: false,
            error: error.message
          });
        }
      }
      
      return formatResponse({
        total: artifact_requests.length,
        successful: results.length,
        failed: errors.length,
        results,
        errors
      });
    }
  • Tool schema definition including name, description, and input schema for batch_get_artifacts, used in tool registration.
    {
      name: "batch_get_artifacts",
      description: "Get multiple artifacts at once",
      inputSchema: {
        type: "object",
        properties: {
          plan_id: { type: "string", description: "Plan ID" },
          artifact_requests: {
            type: "array",
            description: "List of artifact requests",
            items: {
              type: "object",
              properties: {
                node_id: { type: "string", description: "Node ID" },
                artifact_id: { type: "string", description: "Artifact ID" }
              },
              required: ["node_id", "artifact_id"]
            }
          }
        },
        required: ["plan_id", "artifact_requests"]
      }
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic operation. It doesn't disclose whether this is a read-only operation, what permissions are required, how errors are handled, rate limits, or what the return format looks like. 'Get' implies retrieval but lacks behavioral details needed for safe invocation.

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 with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a straightforward batch retrieval operation.

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 2 required parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what artifacts are, how they relate to plans and nodes, what format the response takes, or error conditions. The agent lacks context to use this tool effectively beyond basic parameter passing.

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 fully documents both parameters (plan_id and artifact_requests). The description adds no additional parameter semantics beyond implying batch retrieval. This meets the baseline for high schema coverage where description doesn't need to compensate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get multiple artifacts at once' clearly states the action (get) and resource (artifacts), but it's vague about scope and doesn't distinguish from sibling tools like 'manage_artifact' or 'get_node_context'. It specifies 'multiple' which adds some differentiation from single-get operations, but lacks specificity about what artifacts are in this context.

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 'manage_artifact' or 'get_node_context'. It doesn't mention prerequisites, constraints, or typical use cases. The agent must infer usage from the tool name and parameters alone.

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/TAgents/agent-planner-mcp'

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