cosplaytele-mcp

Overview Schema Source Related Servers Discussions Admin

List gallery sources

list_sources

Read-only

List every gallery source this server can query to obtain source IDs, category slugs, and search/latest support. Call this first to determine which source to use.

Instructions

Return every gallery source this server can query.

Call this first when you need a source id, a category slug, or to check whether a source supports search or latest listings.

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_sources"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Sep 10, 2026

TDQS

A4.3/5.0

Behavior3/5

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

The annotations provide readOnlyHint=true and openWorldHint=false, and the description does not contradict them. It adds a little context by stating the tool returns a list of sources, but does not go into details like pagination or response structure. With annotations covering the safety profile, this is adequate.

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 two sentences, front-loaded with the primary function and then providing concrete usage guidance. There is no wasted wording, and every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with no parameters, and the output schema exists, so the description does not need to explain return values. It fully covers when to use the tool and what it accomplishes. The description is complete for an agent to call it 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?

There are zero parameters, so the schema already fully describes the input. The description adds no parameter-specific information because none is needed. A baseline of 4 is appropriate for a tool with no 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?

The description clearly states the tool returns every gallery source the server can query, which is a specific verb+resource. It also lists concrete use cases (need a source id, category slug, or check search/latest support), distinguishing it from sibling tools that operate on individual items.

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 explicitly says 'Call this first' and enumerates three specific situations where this tool is the appropriate entry point. It doesn't explicitly state when not to use it, but the context makes it clear it's the initial discovery step before using siblings like browse or search.

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

Deploy Server