Skip to main content
Glama

Semerenko Group Public Site MCP

List city guides

sem.list_city_guides
Read-only

Return Semerenko city/location guide URLs.

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

Input Schema

NameRequiredDescriptionDefault
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is clear without the description. The description adds that the payload is URLs (useful given there is no output schema), but says nothing about how the optional search narrows results, whether all guides are returned, or pagination.

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?

One short, front-loaded sentence with no filler; the verb and resource come first. It is efficient rather than padded, though the brevity is achieved partly by omitting needed detail.

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?

This is a low-complexity read-only tool with no output schema, so a short description is defensible. Still, the one optional parameter is undocumented everywhere and the return shape is only hinted at as 'URLs', leaving an agent guessing about filtering behavior.

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 'search' has 0% schema description coverage, so the description is the only place its meaning could be conveyed — and it says nothing at all about it. With one undocumented parameter, the baseline-4 allowance for zero-parameter tools does not apply, and no compensating detail is offered.

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 uses a specific verb ('Return') and a specific resource ('Semerenko city/location guide URLs'), which is enough to separate it from data-returning siblings like sem.market_city or sem.get_property. It stops short of 5 because it never explains what a 'city guide' actually is or how it differs from the property-city listings.

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 exclusions, and no reference to any alternative tool. An agent must guess whether this is the right call when it wants city information versus sem.list_property_cities or sem.market_cities.

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