Skip to main content
Glama
Sign In
Tally

Tally

by bisale24-ops
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Recent activity

recent_activity
Read-onlyIdempotent

View recently recorded household expenses, newest first. Set a limit to control how many entries to display.

Instructions

List what was recorded lately, most recent first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recent_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many entries

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, establishing the safe read-only profile. The description adds the 'most recent first' ordering behavior, but does not disclose what kinds of records are included or how far back 'lately' reaches. There is no contradiction with the annotations.

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 that front-loads the verb and includes the key ordering constraint. There is no filler, repetition of the title, or extraneous content.

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?

For a one-parameter read-only tool with annotations and an output schema, the description is mostly adequate. The main gap is that 'what was recorded lately' is ambiguous about scope—it does not specify whether this lists only expenses or all recorded household actions, so an agent may not know what results to expect.

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%, and the single parameter limit is fully documented with a description, default, minimum, and maximum. The description adds no parameter-level detail, but it does not need to because the schema already carries the meaning.

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 uses the specific verb 'List' and names the resource ('what was recorded lately'), and adds the ordering detail 'most recent first.' This is enough to separate it from siblings like show_balances and record_expense, though 'what was recorded' is slightly broad and could include expenses, settlements, or other household actions.

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 is given about when to use this tool versus alternatives such as show_balances, what_do_i_owe, or undo_last. The recency framing implies a use case, but the description leaves the selection decision entirely to the agent with no exclusions or alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools