Skip to main content
Glama
sameerbajaj

Goodreads MCP

by sameerbajaj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

workflow_status

Read-only

Check local archive status and sync state across all Goodreads resources to identify what is synced and what still needs updating.

Instructions

Show local archive status and sync state for all resources

Input Schema

NameRequiredDescriptionDefault
dbNoDatabase path
csvNoOutput as CSV (table and array responses) (default: false)
yesNoSkip confirmation prompts (for agents and scripts) (default: false)
jsonNoOutput as JSON (default: false)
agentNoSet all agent-friendly defaults (--json --compact --no-input --no-color --yes) (default: false)
plainNoOutput as plain tab-separated text (default: false)
quietNoBare output, one value per line (default: false)
configNoConfig file path
selectNoComma-separated fields to include in output (e.g. --select id,name,status)
compactNoReturn only key fields (id, name, status, timestamps) for minimal token usage (default: false)
deliverNoRoute output to a sink: stdout (default), file:<path>, webhook:<url>
dry-runNoShow request without sending (default: false)
profileNoApply values from a saved profile (see 'goodreads profile list')
timeoutNoRequest timeout (default: 30s)
no-cacheNoBypass response cache (default: false)
no-colorNoDisable colored output (default: false)
no-inputNoDisable all interactive prompts (for CI/agents) (default: false)
idempotentNoTreat already-existing create results as a successful no-op (default: false)
rate-limitNoMax requests per second (0 to disable) (default: 0)
data-sourceNoData source for read commands: auto (live with local fallback), live (API only), local (synced data only) (default: auto)
human-friendlyNoEnable colored output and rich formatting (default: false)

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, destructiveHint=false, and openWorldHint=true. The description adds that the scope is local archive status and sync state across all resources, but it does not elaborate on auth, rate limits, caching, or what the returned status includes. It adds some scope context without contradicting 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?

A single front-loaded sentence with no filler. It communicates the core scope immediately and is appropriately sized for a status command.

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?

There is no output schema, and the description does not explain what 'status' or 'sync state' contains. For a 21-parameter status tool, the minimal description is adequate to identify the command but leaves output expectations and practical usage context under-specified.

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%, so all 21 parameters already have structured descriptions. The tool description adds no parameter-level meaning beyond that, which makes the baseline score of 3 appropriate.

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 states a specific verb and resource: 'Show local archive status and sync state for all resources.' This is clearly a read-only status tool, distinguishable in kind from siblings like workflow_archive and sync, though it does not explicitly name those alternatives.

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?

It gives no explicit guidance on when to use this tool versus workflow_archive, sync, or other siblings. The scope 'for all resources' is stated, but there are no usage conditions, prerequisites, or exclusions.

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