Skip to main content
Glama
Sign In
AnyList MCP Server

AnyList MCP Server

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

anylist_guide

Explains AnyList screens and the sign-in link so you can navigate shopping lists, recipes, and meal plans and complete tasks in the correct order. Call this first.

Instructions

How to work in AnyList (shopping lists, recipes and meal plans): its screens and the sign-in link. Call this 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": "anylist_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in AnyList, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does indicate the guide covers screens and the sign-in link, implying orientation content, but it never says whether the tool is read-only, whether it returns text or links, or how large the payload is.

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?

Two short sentences with no filler; the scope is stated first and the critical 'Call this first' directive is front-loaded in the reader's attention. Nothing would be lost by trimming, and nothing needs adding for clarity.

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 lightweight orientation tool with one optional parameter and no output schema, the description covers the topic surface but not the return shape or safety profile. An agent knows when to call it but not quite what to expect back.

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?

There is a single optional 'task' parameter with 100% schema description coverage, so the schema already explains it as a free-form statement of intent. The description adds nothing about how to phrase that task, so the baseline of 3 applies.

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 names a concrete deliverable: guidance on AnyList screens (shopping lists, recipes, meal plans) plus the sign-in link. That distinguishes it from the sibling UI-action tools (click/type/open/read/status), though 'How to work in AnyList' is broad phrasing rather than a crisp verb+resource statement.

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?

'Call this first' gives an explicit, unambiguous ordering directive that tells the agent when to invoke it relative to the siblings. It stops short of stating any condition under which the guide can be skipped or re-called later.

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