Skip to main content
Glama

Sweeppea MCP

by com.sweeppea.mcp

fetch_todos

Read-onlyIdempotent

Get all To-Do items with pagination (20 per page), search, and advanced filters. ADMIN ONLY: This tool requires admin privileges. Non-admin users will receive a 403 Forbidden error from the API.

fetch_todos

When to use

Get all To-Do items with pagination (20 per page), search, and advanced filters. ADMIN ONLY: This tool requires admin privileges. Non-admin users will receive a 403 Forbidden error from the API.

Parameters to validate before calling

  • page (number, optional) — Page number (default: 1, 20 items per page).

  • search (string, optional) — Search by title or description (case-insensitive).

  • status (string, optional) — one of: pending, completed — Filter by status: "pending" or "completed".

  • priority (number, optional) — one of: 1, 2, 3 — Filter by priority: 1 = Low, 2 = Medium, 3 = High.

  • resource (string, optional) — Filter by resource affected (e.g. "renaissance", "api", "aws", "general").

  • pinned (boolean, optional) — Filter pinned items only when true.

  • date_from (string, optional) — Start date filter in ISO 8601 format (e.g. "2026-01-01").

  • date_to (string, optional) — End date filter in ISO 8601 format (e.g. "2026-12-31").

  • year (number, optional) — Filter by creation year (ignored if date_from/date_to provided).

  • month (number, optional) — Filter by creation month 1-12 (requires year parameter).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default: 1, 20 items per page).
yearNoFilter by creation year (ignored if date_from/date_to provided).
monthNoFilter by creation month 1-12 (requires year parameter).
pinnedNoFilter pinned items only when true.
searchNoSearch by title or description (case-insensitive).
statusNoFilter by status: "pending" or "completed".
date_toNoEnd date filter in ISO 8601 format (e.g. "2026-12-31").
priorityNoFilter by priority: 1 = Low, 2 = Medium, 3 = High.
resourceNoFilter by resource affected (e.g. "renaissance", "api", "aws", "general").
date_fromNoStart date filter in ISO 8601 format (e.g. "2026-01-01").

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive hints. The description adds valuable behavioral context: admin privileges required, 403 for non-admins, and pagination defaults. No contradictions with annotations.

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?

The description is well-structured with headings but is verbose and redundant, repeating the same main sentence twice and duplicating the schema's parameter descriptions. It would be more concise by keeping only the core sentence and admin warning.

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

Completeness4/5

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

With no output schema, the description reasonably covers purpose, admin restriction, pagination, and all parameter details. It doesn't describe the response format, but the tool's name and read-only behavior imply the return of todo items.

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?

All 10 parameters are fully described in the input schema, and the description's parameter list largely duplicates that information without adding new semantic meaning. Since schema coverage is 100%, a baseline of 3 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 retrieves all To-Do items with pagination, search, and advanced filters. It specifies the resource and operation, distinguishing it from create/update/delete todo tools.

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?

The description includes a 'When to use' section and clearly notes the ADMIN ONLY restriction, which is a key usage condition. It doesn't explicitly mention alternative tools or exclusions, but the purpose is unambiguous given the tool name and sibling context.

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

All Sweeppea MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation4/5

Most tools follow a clear resource+action pattern (fetch_* for lists, get_* for single items, create/update/delete for writes), making them distinguishable. A few near-overlaps exist (fetch_billing_transactions vs fetch_wallet_transactions, draw_winners vs schedule_drawing) but the descriptions clarify the boundaries.

Naming Consistency4/5

Tool names consistently use snake_case verb_noun, with fetch_ for list operations and get_ for single-item retrieval. Some verb variation (add_participant, count_participants, draw_winners, schedule_drawing) deviates from the dominant create/fetch/update/delete pattern but remains predictable and readable.

Tool Count1/5

With 83 tools, this is far beyond a well-scoped server (typically 3-15, with 25+ considered too many). Even though the platform has broad functionality, the sheer number of tools creates significant agent confusion and selection overhead.

Completeness4/5

The sweepstakes domain is thoroughly covered: lifecycle management, participants, groups, rules, drawings, winners, calendar, notes, todos, tickets, surveys, invoices, billing, files, and entry settings. A few minor gaps exist (e.g., no general participant field update, no archive action) but the surface is remarkably complete for its scope.

Resources