jsonplaceholder-mcp

get_todos

Retrieve todos from JSONPlaceholder, optionally filtering by todo ID or user ID.

Instructions

Get todos from JSONPlaceholder. Can retrieve all todos, a specific todo by ID, or filter by user ID.

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

Input Schema

Name	Required	Description	Default
`id`	No	Optional todo ID to retrieve a specific todo
`userId`	No	Optional user ID to retrieve todos for a specific user

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. The verb 'Get' suggests a read-only operation, and the description details retrieval modes, but it does not explicitly state read-only semantics, error behavior, or response format. This is partial transparency.

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?

The description is a single, efficient sentence that front-loads the resource and immediately explains the parameter usage. There is no wasted wording, and the structure is clear and scannable.

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?

For a simple read tool with two optional parameters and no output schema, the description covers the core functionality and parameter interactions. It does not mention return format or explicitly confirm read-only behavior, but given the low complexity, it is adequately complete.

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 coverage is 100%, but the description adds meaning by mapping parameters to specific retrieval modes. It clarifies that omitting both parameters returns all todos, while providing 'id' or 'userId' filters accordingly. This goes beyond the schema's per-field descriptions.

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 it retrieves todos from JSONPlaceholder, using the specific verb 'Get' and resource 'todos'. It further distinguishes from sibling tools (posts, users, comments) by the resource type and explicitly lists three retrieval modes (all, by ID, by user ID).

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 explains the three invocation scenarios (all todos, by ID, or by user ID), giving clear context for when to use the tool and which parameters to provide. It does not explicitly mention alternatives or exclusions, but the resource difference from siblings makes the usage straightforward.

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

Deploy Server