Skip to main content
Glama

mcp-server

by ar.com.muovi

List cities

muovi_list_cities
Read-only

List every Argentine city Muovi serves, with active neighborhoods nested under each. Each city has a stable slug (used as the city parameter on muovi_search_professionals) and a human-readable name. Each neighborhood has its own slug (used as the neighborhood parameter on muovi_search_professionals). Call this when you need to resolve a user's location wording to a Muovi city or neighborhood slug.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. Description adds value by specifying the structure (nested neighborhoods, slug/name pairs) and linking to other tools, but does not contradict annotations.

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?

Three sentences, front-loaded with purpose, followed by specific details and usage guidance. No wasted words.

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

Completeness5/5

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

For a parameterless tool, description fully explains output (cities with neighborhoods, slugs) and usage context, sufficient for an agent to select and invoke correctly.

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?

No parameters; baseline score of 4 applied. Description does not need to add parameter meaning, but it clarifies the output format which indirectly supports parameter usage for other tools.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it lists Argentine cities with nested neighborhoods, specifying slugs for use in other tools, which distinguishes it from siblings like muovi_search_professionals.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly describes when to use: 'Call this when you need to resolve a user's location wording to a Muovi city or neighborhood slug.' Provides clear context for invocation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: generating deep links, fetching professional profiles, reviews, listing cities and services, and searching professionals. No overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent 'muovi_verb_noun' snake_case pattern (e.g., muovi_search_professionals, muovi_list_cities), making it predictable.

Tool Count5/5

Six tools cover the necessary operations for a service professional platform without being excessive or insufficient. Each tool serves a clear need.

Completeness5/5

The tool set covers discovery (search, list cities/services), detailed information (professional, reviews), and the intended action (deep link for task creation). The lack of server-side task creation is by design, so the surface is complete.

Resources