Skip to main content
Glama

FIDES Ecosystem Explorer

list_site_content

Read-onlyIdempotent

List every published FIDES Community website page and post with its title, slug and up to 24 headings (headingCount gives the full count). WordPress does not rank or filter this list: inspect it yourself to choose the relevant document, then call read_site_page. Use catalog tools instead for concrete catalog records.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the description's job is to add context, which it does: only published content is returned, WordPress applies no ranking or filtering, headings are capped at 24 with headingCount giving the true total. It stops short of describing pagination, ordering, or the volume of results, which would matter for a whole-site listing.

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?

Three sentences, front-loaded with what is returned, then the caller's responsibility, then the exclusion. Every sentence carries a distinct piece of information with no repetition of the annotations.

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?

There is no output schema, so the description compensates by describing the per-record fields and the 24-heading truncation up front. Combined with annotations covering safety and the explicit hand-off to read_site_page, an agent has everything needed to call it and act on the result.

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 is 4; there is no parameter semantics to add. What the description does instead is document the shape of each returned record (title, slug, headings, headingCount), which usefully frames why the caller gets no filtering arguments.

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?

States a specific verb and resource: lists every published FIDES Community website page and post, and names the returned fields (title, slug, up to 24 headings, headingCount). It explicitly separates itself from read_site_page and from the catalog tools, so an agent can pick it without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit workflow: inspect this unranked list yourself to pick the relevant document, then call read_site_page. It also gives an exclusion — use catalog tools for concrete catalog records — so both the alternative and the condition that selects it are covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources