Skip to main content
Glama
SannketNikam

Demo MCP Server

by SannketNikam

list_expenses

Retrieve expense entries for a specific date range to track spending patterns and manage budgets effectively.

Instructions

List expense entries within an inclusive date range.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_dateYes
end_dateYes

Implementation Reference

  • main.py:58-75 (handler)
    The handler function for the 'list_expenses' tool, decorated with @mcp.tool() for registration in FastMCP. It asynchronously queries the SQLite database for expenses within the given date range and returns a list of expense dictionaries.
    @mcp.tool()
    async def list_expenses(start_date, end_date):  # Changed: added async
        '''List expense entries within an inclusive date range.'''
        try:
            async with aiosqlite.connect(DB_PATH) as c:  # Changed: added async
                cur = await c.execute(  # Changed: added await
                    """
                    SELECT id, date, amount, category, subcategory, note
                    FROM expenses
                    WHERE date BETWEEN ? AND ?
                    ORDER BY date DESC, id DESC
                    """,
                    (start_date, end_date)
                )
                cols = [d[0] for d in cur.description]
                return [dict(zip(cols, r)) for r in await cur.fetchall()]  # Changed: added await
        except Exception as e:
            return {"status": "error", "message": f"Error listing expenses: {str(e)}"}
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It implies a read operation ('List') but doesn't address permissions, pagination, rate limits, or response format. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 waste—it directly states the tool's function and scope without redundancy. It's appropriately sized and front-loaded, making it easy to parse quickly.

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?

Given no annotations, 0% schema coverage, and no output schema, the description is incomplete. It lacks details on behavioral traits, parameter usage, and return values, which are critical for a tool with two required parameters and potential complexity in expense data handling.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It mentions 'inclusive date range' which hints at the two parameters, but doesn't explain date formats, time zones, or validation rules. This adds minimal semantic value beyond the schema titles.

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 ('List') and resource ('expense entries') with specific scope ('within an inclusive date range'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'summarize' which might also handle expense data, so it doesn't reach the highest 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 'add_expense' or 'summarize'. It mentions date range filtering but doesn't specify prerequisites, exclusions, or comparative contexts, leaving usage decisions to inference.

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/SannketNikam/test-remote-mcp-server'

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