Skip to main content
Glama
chrischall

OurFamilyWizard MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

ofw_list_expenses

Read-only

Retrieve OurFamilyWizard expense records page by page; pass the 1-based page and size, then use nextPage from the response to continue until it is null.

Instructions

List OurFamilyWizard expenses. OFW pages this endpoint with 1-based page/size parameters; its older start/max parameters are ignored and repeatedly return page 1. The response leads with hasMore and nextPage (null when exhausted) before the records. Continue by passing nextPage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number (default 1). To continue, pass the nextPage returned by the previous response.
sizeNoRequested page size (default 20). OFW may cap or normalize this value.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.20.0
    • removedInput schema / properties / max
      Removed value: -{
-  "description": "Max results (default 20)",
-  "maximum": 9007199254740991,
-  "minimum": 1,
-  "type": "integer"
-}
    • addedInput schema / properties / page
      Added value: +{
+  "description": "1-based page number (default 1). To continue, pass the nextPage returned by the previous response.",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / size
      Added value: +{
+  "description": "Requested page size (default 20). OFW may cap or normalize this value.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • removedInput schema / properties / start
      Removed value: -{
-  "description": "Start offset, 0-based (default 0). To continue a listing, pass the `nextStart` from the previous response.",
-  "maximum": 9007199254740991,
-  "minimum": 0,
-  "type": "integer"
-}
  2. Changed1 schema field changedv2.17.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed1 schema field changedv2.14.0
    • changedInput schema / properties / start / description
      Previous value: -"Start offset (default 0)"New value: +"Start offset, 0-based (default 0). To continue a listing, pass the `nextStart` from the previous response."
  4. First observedv2.8.0

TDQS

A4.4/5.0
Behavior5/5

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

With only readOnlyHint available in annotations, the description adds substantial non-obvious behavior: the start/max parameters are silently ignored and always return page 1, and the response payload leads with hasMore/nextPage before records. This is exactly the kind of quirk an agent cannot infer from structured fields.

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?

Three tightly written sentences, front-loaded with the resource and then the pagination pitfall and continuation pattern. No filler; every sentence contributes actionable information.

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?

There is no output schema, so the description compensates by describing the response shape (hasMore, nextPage, records) and the continuation contract. Combined with the annotations and full schema coverage, the agent has everything needed to call and iterate this endpoint.

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?

Schema description coverage is already 100%, so the baseline is 3. The description nonetheless adds semantic value by explaining the 1-based paging convention, the pitfall of the ignored start/max parameters, and how page/size relate to nextPage, which goes beyond the schema text.

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?

States a specific verb+resource ('List OurFamilyWizard expenses'), which clearly separates it from write siblings like ofw_create_expense or ofw_update_expense. It does not explicitly distinguish itself from the closer sibling ofw_get_expense_totals, so it stops short of the top score.

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

Usage Guidelines4/5

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

Gives concrete operational guidance for the tool's main workflow: use 1-based page/size, ignore start/max, and continue with nextPage. It lacks any when-not or alternative-tool guidance (e.g., vs. get_expense_totals), so it is clear but not complete.

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