CoworkingView

List coworking locations

list_coworking_locations

Read-onlyIdempotent

Lists every country, city and zone where CoworkingView has coworking spaces, with the exact slugs required by the other tools and how many spaces each place has. A "zone" is a district inside a city (for example "mitte" inside "berlin"). Call this before searching whenever the user names a place, because every filter takes a lowercase slug and a guessed slug returns an empty result rather than an error. Also answers "which cities do you cover?" directly.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`locale`	No	Language for names and descriptions. Set from the user's language: 'de' for German, 'es' for Spanish, otherwise 'en'.	en
`country`	No	Optional ISO country code or country slug to narrow the list, e.g. 'DE' or 'germany'. Omit to list everything.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`cities`	Yes
`countries`	Yes
`totalSpaces`	Yes

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already indicate read-only and idempotent behavior. The description adds that a guessed slug returns empty rather than an error, which is helpful beyond annotations.

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?

The description is well-structured and informative, but slightly verbose with multiple sentences. It front-loads the key output and then gives context.

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?

Given the tool's simplicity, full schema descriptions, and annotations, the description covers usage, output, and error behavior completely.

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

Parameters3/5

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

Schema description coverage is 100% with detailed parameter descriptions. The description does not add significant new meaning to the parameters beyond what the schema provides.

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?

The description clearly states the tool lists countries, cities, and zones with slugs and counts. It distinguishes from siblings by emphasizing the slug requirement for other tools.

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?

The description explicitly says to call this before searching when a user names a place, because filters need slugs. It also notes that this tool answers coverage questions directly.

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

All CoworkingView tools Inspect

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 distinct purpose: comparing spaces, best value ranking, filter options, market rates, operator profiles, place guides, single space details, location listing, query resolution, and searching. No overlap.

Naming Consistency4/5

Naming follows a clear verb_noun scheme with snake_case, though slight variation (get_best_coworking vs get_coworking_*) is minor and still predictable.

Tool Count5/5

10 tools is well-scoped for the informational coworking domain, covering all necessary operations without excess.

Completeness5/5

Covers all obvious needs: location discovery, query resolution, search, details, comparison, market rates, filter options, operator info, and editorial guides. No dead ends.

Resources

Need Help?