Skip to main content
Glama
G-Hensley
by G-Hensley

Get Goals

get_goals

Retrieve current goals and their progress with optional filters by category or status to track personal and professional objectives.

Instructions

Get current goals and their progress

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoFilter by category (business, technical, community, content)
statusNoFilter by goal status

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYes

Implementation Reference

  • Async handler function for the 'get_goals' tool. Reads goals from 'profile/goals/2026-goals.json', optionally filters by category and status, and returns the matching goals with their category title, goal text, status, target date, and metrics.
    async ({ category, status }) => {
      const goals = await readJsonFile<GoalsData>("profile/goals/2026-goals.json");
      const result: GoalResult[] = [];
    
      for (const [cat, data] of Object.entries(goals.categories)) {
        if (category && cat !== category) continue;
        for (const goal of data.goals) {
          if (status && goal.status !== status) continue;
          result.push({
            category: cat,
            categoryTitle: data.title,
            goal: goal.goal,
            status: goal.status,
            target_date: goal.target_date,
            metrics: goal.metrics,
          });
        }
      }
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • GoalResult interface defining the output shape: category, categoryTitle, goal, status, target_date, and metrics.
    export interface GoalResult {
      category: string;
      categoryTitle: string;
      goal: string;
      status: string;
      target_date: string;
      metrics: GoalMetrics;
    }
  • GoalMetrics interface with target and current fields.
    export interface GoalMetrics {
      target: string;
      current: string;
    }
  • Goal interface with id, goal, status, target_date, and metrics fields.
    export interface Goal {
      id: string;
      goal: string;
      status: string;
      target_date: string;
      metrics: GoalMetrics;
    }
  • api/mcp.ts:158-169 (registration)
    Registration of the 'get_goals' tool via server.registerTool, including its title, description, inputSchema (optional category and status filters), and outputSchema.
    // Tool: Get Goals
    server.registerTool(
      "get_goals",
      {
        title: "Get Goals",
        description: "Get current goals and their progress",
        inputSchema: {
          category: z.string().optional().describe("Filter by category (business, technical, community, content)"),
          status: z.enum(["in_progress", "not_started", "completed"]).optional().describe("Filter by goal status"),
        },
        outputSchema: textContentOutputSchema,
      },
Behavior2/5

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

No annotations provided. Description does not disclose behavioral traits: no mention of read-only nature, data freshness, pagination, or rate limits. Implies read access but not explicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single short sentence, concise but not richly informative. Could include usage hints or typical scenarios without excess length.

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?

Output schema exists, so return values need not be explained. However, description lacks mention of available categories, statuses, or that progress is included. For a simple tool, more context would improve completeness.

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% (both parameters have descriptions). Description adds no additional meaning beyond schema: 'category' and 'status' filters are already documented in the schema. Baseline 3 applies.

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?

Description clearly states 'Get current goals and their progress', which specifies the verb 'Get' and resource 'goals and their progress'. It distinguishes from sibling tools like 'update_goal_progress' (update vs get) and other 'get_*' tools, though 'current' is slightly ambiguous.

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 on when to use this tool over alternatives like 'get_projects' or 'update_goal_progress'. No mention of filtering by category or status, or prerequisites.

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/G-Hensley/myself-mcp-server'

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