Skip to main content
Glama
Sign In
LightCMS

LightCMS

by metavert-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

List Import Sources

list_import_sources
Read-only

Retrieve every RSS or Atom feed configured as an import source in LightCMS to audit, verify, or manage content ingestion endpoints.

Instructions

List all configured RSS/Atom import sources

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv7.3.4

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered externally. The description only adds that sources are RSS/Atom-typed and that all configured entries are returned without filtering; it says nothing about pagination or result size.

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?

A single, front-loaded sentence with no filler or redundancy. It is terse to the point of under-specification, but as a conciseness measure it is close to ideal.

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 no-argument, read-only listing tool with annotations covering the safety profile and no output schema, the description supplies what an agent needs to invoke it. The only meaningful gap is the absence of routing guidance versus list_import_jobs.

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 zero parameters, so the baseline of 4 applies. There is nothing in the schema for the description to explain or compensate for.

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?

States a specific verb ('List') and a specific resource ('configured RSS/Atom import sources'), which is enough for an agent to distinguish it from mutation siblings such as create_import_source, update_import_source, and delete_import_source. It does not, however, explicitly distinguish itself from the closely related list_import_jobs.

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?

There is no when-to-use guidance, no prerequisite or exclusion statements, and no mention of the nearest alternative (list_import_jobs, trigger_import_source). Usage is only implied by the word 'configured'.

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