BJJ Square

List covered places

list_places

Read-onlyIdempotent

Countries covered by BJJ Square with gym counts, or, with a country code, the cities of that country with gym counts (largest 200). Use it to check coverage before find_gyms.

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": "list_places"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No	Language of the returned bjjsquare.com links: it, en, es, pt, fr or de. Default en.
`country`	No	ISO 3166-1 alpha-2 code. Omit to list countries.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 1, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds the 200-city limit detail, which is useful behavioral context 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?

One dense sentence covering both modes and the city limit, plus a short usage sentence. Efficient and front-loaded, though the first sentence is somewhat packed.

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

Completeness4/5

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

Given a read-only tool with full annotation coverage, 2 well-documented parameters and no output schema, the description covers the essential modes and limits. The return structure (gym counts) is mentioned, though not detailed.

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 coverage is 100%, so both parameters are fully documented in the schema. The description only explains the mode switch based on the country parameter, which the schema already implies. Baseline 3 is appropriate.

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?

States a specific verb+resource ('list covered places') and clearly distinguishes two modes: countries by default, cities when a country code is given. This differentiates it from siblings find_gyms and get_gym.

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

Usage Guidelines4/5

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

Explicitly says 'Use it to check coverage before find_gyms', giving clear when-to-use context. It doesn't name when not to use it, but the alternative is obvious from the sibling tools.

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

All BJJ Square tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?