Skip to main content
Glama

Semerenko Group Public Site MCP

Get public site inventory

sem.get_site_inventory
Read-only

Return active plugin/MU plugin summaries, public post type counts, tool inventory, and safe boundaries.

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.get_site_inventory"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds some value by emphasizing "active" filtering and "public" data plus "safe boundaries", implying no secrets or private content is exposed. It does not describe result shape, pagination, or what "safe boundaries" concretely means.

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 that lists the returned categories with no filler. The term "safe boundaries" is jargon that a reader cannot resolve, which keeps it from a 5.

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

Completeness3/5

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

With no parameters and no output schema, the description bears the full burden of explaining what comes back, and it only names four categories without describing their shape or size. It is adequate to decide whether to call the tool, but thin for interpreting 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 there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies a single no-argument snapshot call.

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 concrete verb ("Return") and enumerates the specific contents of the inventory: active plugin/MU plugin summaries, public post type counts, tool inventory, and safe boundaries. An agent can tell this is an aggregate site-overview read. It does not, however, distinguish itself from siblings like get_plugin_inventory or get_tool_inventory, whose subject matter it overlaps.

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 statement of when to call this versus the narrower plugin and tool inventory siblings, nor any prerequisite or exclusion. Usage is only inferable from the word "inventory" being broader than the sibling names.

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