Skip to main content
Glama

List unassigned count lists

list_unassigned_count_lists
Read-onlyIdempotent

List the count lists saved from the phone that are not in any count yet, newest first, with their totals and who created them (id and name only). At most 200 are returned, and truncated says if there are more. Use add_count_lists to put them in a count. Requires the stock plan feature.

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": "list_unassigned_count_lists"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description layers on real operational detail: newest-first ordering, a hard cap of 200, and a truncated flag signaling more results. It also states the stock plan feature prerequisite and which fields come back (totals, creator id and name).

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 tight sentences, front-loaded with what is returned and in what order, followed by the limit/truncation caveat, the next-step pointer, and the prerequisite. Every clause carries distinct information.

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 carries the burden of describing returns and does so (totals, creator id/name, ordering, truncation cap) plus the feature prerequisite. Minor omission is what 'totals' aggregates, but overall it is complete enough to call correctly.

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?

The tool takes no parameters, so the baseline is 4 and there is nothing the description could add. It correctly spends no words on argument semantics and instead documents result shape.

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?

Names a specific verb and resource plus a precise scope: count lists saved from the phone that are not in any count yet. The 'unassigned' qualifier separates it cleanly from list_counts and points to add_count_lists for the follow-up action.

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 makes the use case clear (finding unassigned phone-saved lists) and names the natural next step, add_count_lists, for assigning them. It never explicitly contrasts with list_counts for already-assigned lists, so the alternative routing is implied rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources