Skip to main content
Glama
gabeosx

freedcamp

freedcamp_list_tasks

Retrieve all tasks from a Freedcamp project with details including status, priority, due dates, and assignee information.

Instructions

Retrieve all tasks in the configured Freedcamp project. Returns task details including ID, title, description, status, priority, due date, and assignee information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the freedcamp_list_tasks tool. It builds auth params, constructs the API URL for the project tasks, fetches the data, and returns the tasks as formatted JSON or an error message.
    async () => {
      const authParams = buildFreedcampAuthParams({
        api_key: config.apiKey,
        api_secret: config.apiSecret,
      });
    
      const params = new URLSearchParams({
        ...authParams,
        project_id: config.projectId,
      });
      const url = `https://freedcamp.com/api/v1/tasks/?${params.toString()}`;
      console.log("Making request to Freedcamp API with URL:", url);
      const resp = await fetch(url, {
        method: "GET",
      });
      const json = (await resp.json()) as any;
      console.log("Freedcamp API response:", json);
      if (!resp.ok || (json && json.http_code >= 400)) {
        return {
          content: [
            { type: "text", text: `Error: ${json?.msg || resp.statusText}` },
            { type: "text", text: JSON.stringify(json) }
          ]
        };
      }
      return {
        content: [
          { type: "text", text: JSON.stringify(json?.data?.tasks || [], null, 2) },
        ]
      };
    }
  • The input schema and metadata (description, annotations) for the freedcamp_list_tasks tool. Note: inputSchema is empty as no parameters are required.
    {
      description: "Retrieve all tasks in the configured Freedcamp project. Returns task details including ID, title, description, status, priority, due date, and assignee information.",
      inputSchema: {},
      annotations: {
        title: "List Tasks"
      }
    },
  • The server.registerTool call that registers the freedcamp_list_tasks tool, including schema and inline handler function.
    server.registerTool("freedcamp_list_tasks",
      {
        description: "Retrieve all tasks in the configured Freedcamp project. Returns task details including ID, title, description, status, priority, due date, and assignee information.",
        inputSchema: {},
        annotations: {
          title: "List Tasks"
        }
      },
      async () => {
        const authParams = buildFreedcampAuthParams({
          api_key: config.apiKey,
          api_secret: config.apiSecret,
        });
    
        const params = new URLSearchParams({
          ...authParams,
          project_id: config.projectId,
        });
        const url = `https://freedcamp.com/api/v1/tasks/?${params.toString()}`;
        console.log("Making request to Freedcamp API with URL:", url);
        const resp = await fetch(url, {
          method: "GET",
        });
        const json = (await resp.json()) as any;
        console.log("Freedcamp API response:", json);
        if (!resp.ok || (json && json.http_code >= 400)) {
          return {
            content: [
              { type: "text", text: `Error: ${json?.msg || resp.statusText}` },
              { type: "text", text: JSON.stringify(json) }
            ]
          };
        }
        return {
          content: [
            { type: "text", text: JSON.stringify(json?.data?.tasks || [], null, 2) },
          ]
        };
      }
    );
  • Helper function buildFreedcampAuthParams used in the handler to generate authentication parameters (api_key, timestamp, hash for secured API) for the Freedcamp API request.
    export function buildFreedcampAuthParams(auth: FreedcampAuth): Record<string, string> {
      if (auth.api_secret) {
        const timestamp = Math.floor(Date.now() / 1000);
        const hash = generateFreedcampHash(auth.api_key, auth.api_secret, timestamp);
        return {
          api_key: auth.api_key,
          timestamp: String(timestamp),
          hash,
        };
      } else {
        return {
          api_key: auth.api_key,
        };
      }
Behavior3/5

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

Annotations only provide a title ('List Tasks'), so the description carries the burden of behavioral disclosure. It adds value by specifying the return format (task details like ID, title, status, etc.) and implying a read-only operation, but doesn't cover aspects like error handling, pagination, or rate limits. No contradiction with annotations exists.

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, well-structured sentence that efficiently conveys the action, scope, and return details without redundancy. It's front-loaded with the core purpose, but could be slightly more concise by integrating the return information more seamlessly.

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 simplicity (0 parameters, no output schema, minimal annotations), the description is adequate but has gaps. It explains what the tool does and what it returns, but lacks usage guidelines, error handling, or behavioral nuances. For a list tool with no complex inputs, this is minimally viable but not comprehensive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately omits parameter details, focusing on the tool's function and output. This meets the baseline for zero parameters, but doesn't exceed expectations with extra context.

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 verb ('Retrieve') and resource ('all tasks in the configured Freedcamp project'), making the purpose evident. It distinguishes from siblings by focusing on listing rather than adding, deleting, or updating tasks. However, it doesn't explicitly contrast with sibling tools, preventing a perfect score.

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 'freedcamp_add_task' or 'freedcamp_update_task'. It lacks context about prerequisites (e.g., needing a configured project) or exclusions, leaving usage decisions to inference from the tool name 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/gabeosx/freedmcpcamp'

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