Skip to main content
Glama
Sign In
Open Search MCP

Open Search MCP

by flyanima
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

jsonplaceholder_albums

Get test albums data from JSONPlaceholder. Optionally specify a user ID (1-10) or limit the number of albums returned (up to 100, default 10).

Instructions

Get test albums data from JSONPlaceholder

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

Input Schema

NameRequiredDescriptionDefault
userIdNoUser ID to get albums for (1-10, optional)
limitNoMaximum number of albums to return (1-100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states it 'gets' data, implying a read operation, but lacks details on authentication, rate limits, or potential side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is a single, clear sentence with no wasted words. It is appropriately concise for a simple tool.

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?

Given low complexity (two optional params, no output schema), the description is minimally complete but could mention return format or that userId is optional for filtering.

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 baseline is 3. The description adds no extra meaning beyond what the schema already provides for the two parameters.

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?

Description clearly states the tool retrieves test albums data from JSONPlaceholder, using a specific verb and resource. It distinguishes itself from sibling tools like jsonplaceholder_posts or jsonplaceholder_comments which target different resources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. The description implies it's for fetching test album data, but does not mention use cases 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