Skip to main content
Glama
jmjeong

Whooing MCP

by jmjeong

whooing_sections

Read-only

List all budget sections (가계부) in your Whooing account to view expense categories.

Instructions

List all sections (가계부) in the Whooing account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler for 'whooing_sections' that calls the Whooing API 'sections.json' endpoint and formats the result.
    // whooing_sections — List sections
    server.registerTool(
      "whooing_sections",
      {
        description: "List all sections (가계부) in the Whooing account",
        inputSchema: {},
        annotations: { readOnlyHint: true },
      },
      async () => {
        const results = await client.apiGet("sections.json");
        const text = formatSections(
          results as Parameters<typeof formatSections>[0]
        );
        return { content: [{ type: "text", text }] };
      }
    );
  • The SectionItem interface and formatSections helper that formats the section list output.
    interface SectionItem {
      section_id: string;
      title: string;
      memo?: string;
      currency?: string;
    }
    
    export function formatSections(results: SectionItem[]): string {
      const lines: string[] = [];
      lines.push("## 가계부 (Section) 목록");
      lines.push("");
    
      if (!Array.isArray(results) || results.length === 0) {
        lines.push("가계부가 없습니다.");
        return lines.join("\n");
      }
    
      for (const section of results) {
        const currency = section.currency ? ` [${section.currency}]` : "";
        const memo = section.memo ? ` — ${section.memo}` : "";
        lines.push(`- ${section.section_id}: ${section.title}${currency}${memo}`);
      }
    
      return lines.join("\n");
    }
  • Registration of the 'whooing_sections' tool with its description and input schema (empty), registered via server.registerTool().
    server.registerTool(
      "whooing_sections",
      {
        description: "List all sections (가계부) in the Whooing account",
        inputSchema: {},
        annotations: { readOnlyHint: true },
      },
  • The formatSections function that renders sections into human-readable text output.
    export function formatSections(results: SectionItem[]): string {
      const lines: string[] = [];
      lines.push("## 가계부 (Section) 목록");
      lines.push("");
    
      if (!Array.isArray(results) || results.length === 0) {
        lines.push("가계부가 없습니다.");
        return lines.join("\n");
      }
    
      for (const section of results) {
        const currency = section.currency ? ` [${section.currency}]` : "";
        const memo = section.memo ? ` — ${section.memo}` : "";
        lines.push(`- ${section.section_id}: ${section.title}${currency}${memo}`);
      }
    
      return lines.join("\n");
    }
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description does not need to add more. It adds context that sections refer to 가계부, which is helpful.

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?

Single sentence, no wasted words, and directly conveys the tool's action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list operation with no parameters and read-only annotation, the description is fully adequate.

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?

No parameters exist, so the description does not need to explain them. Baseline score of 4 is appropriate.

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 clearly states the tool lists all sections (가계부) in the Whooing account, with a specific verb and resource, distinguishing it from sibling tools that deal with entries, accounts, or budgets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives, but the purpose is clear enough that an agent can infer its usage for listing sections.

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/jmjeong/whooing-mcp'

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