Skip to main content
Glama

Semerenko Group Public Site MCP

List content silos

sem.list_silos
Read-only

List the organized content silos (each is a hub-and-spoke category, for example the buy category silo) with hub URL, spoke count, topic count, and status.

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": "sem.list_silos"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is handled. The description adds genuine value beyond that by enumerating the fields returned (hub URL, spoke count, topic count, status), which matters because no output schema exists. It stops short of saying whether the list is paginated or bounded.

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; the parenthetical definition of a silo earns its place because "silo" is domain jargon. Only minor cost is that the return-field list is packed into the same clause rather than separated.

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 parameterless, read-only listing tool with no output schema, the description covers what the tool returns well enough for an agent to reason about the response. The remaining gap is scale behavior — whether all silos come back at once or the result is capped.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. Nothing in the text misleads about inputs.

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?

Uses a specific verb and resource ("List the organized content silos") and goes further by defining what a silo is ("a hub-and-spoke category, for example the buy category silo"), so an agent knows the shape of the entity. It does not explicitly distinguish itself from the sibling sem.get_silo, leaving the list-vs-single-fetch distinction to inference.

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?

Usage is only implied by the verb "list" — an agent can infer this is the enumeration tool and sem.get_silo is the single-item lookup, but the description never says when to choose one over the other. No prerequisites, pagination caveats, or filters (there are none) are mentioned.

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