Skip to main content
Glama

Semerenko Group Public Site MCP

Get one content silo

sem.get_silo
Read-only

Return the full structure of one silo by category: its hub, sub-hubs, every spoke page (title, url, id, type), topic total, build rules, and status.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category": "<category>"
    },
    "name": "sem.get_silo"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 safety is covered before the description is read. The description adds valuable behavior the annotations do not: the call is a full, single-silo structural dump including build rules and status, which tells the agent to expect a large detail payload rather than a summary. It stops short of noting any size, caching, or failure behavior when a category is unknown.

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?

One front-loaded sentence with the verb first and the payload enumerated in a compact list; every clause adds information and there is no filler or redundancy.

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?

With no output schema, the description correctly spends its words describing return contents, so an agent knows what comes back from a low-complexity, single-parameter read tool. The remaining gap is the category value format, which is undocumented in both schema and description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'category' has 0% schema description coverage, so the description must carry the meaning — but 'by category' merely restates the parameter name. It does not say whether the value is a slug, display name, or id, nor where valid categories come from (presumably sem.list_silos), leaving the agent to guess the input format.

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?

The description gives a specific verb and resource ('Return the full structure of one silo') and enumerates exactly what that structure contains (hub, sub-hubs, spoke pages with title/url/id/type, topic total, build rules, status). This clearly separates it from a listing tool like sem.list_silos, but it never names an alternative, so the differentiation is inferred rather than stated.

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: an agent can infer 'use this to drill into a single category's silo' from the phrase 'one silo by category'. There is no explicit when-to-use, when-not-to-use, or pointer to sem.list_silos for discovery versus this detailed fetch, and no note that the category must already exist.

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