Find cities in a province by entering a province slug or name fragment. Retrieve available city options to navigate Sheypoor classifieds.
List cities within a province (by province slug or name fragment).
| Name | Required | Description | Default |
|---|---|---|---|
| province | Yes | Province slug or name fragment |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It only states the purpose and does not disclose any behavioral traits such as pagination, ordering, authentication requirements, or error behavior. This is a significant gap for a tool that might return many cities.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence with no redundancy. It front-loads the core action and scope.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list tool with one parameter and no output schema, the description provides the essential information to call it. It could mention response format or limitations, but it's acceptable for the complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description for the province parameter already explains it is a slug or name fragment. The tool description repeats this and adds the context that it filters cities within that province, which is a small addition. Given 100% schema coverage, this is adequate but not exceptional.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (List), the resource (cities), and the scope (within a province), and specifies the input format (slug or name fragment). This distinguishes it from list_provinces, which lists provinces, and makes the tool's purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when you need cities for a given province, and the sibling list_provinces suggests the alternative for listing provinces. However, it doesn't explicitly state when not to use it or mention alternatives, so it's not fully explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.