Skip to main content
Glama

QDev

List places with events

list_places
Read-onlyIdempotent

The places that have upcoming quantum computing events: continents, countries, states where a country is searched by state, and cities, each with its number of events. Use the codes or names it returns as filters for list_events.

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

NameRequiredDescriptionDefault
continentNoOnly this continent: its code (EU, NA, AS, OC, SA, AF) or its name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and a closed domain (openWorldHint=false), so the safety profile is covered. The description adds genuinely new behavior: the result is a four-level geographic hierarchy scoped to 'upcoming' events, with per-place event counts, and its output values are meant to be reused as filters elsewhere.

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?

Two sentences, front-loaded with the resource and followed by the consumption instruction — efficient and scannable. The phrase 'states where a country is searched by state' is awkwardly worded and slightly obscures the hierarchy rule it is trying to convey.

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?

For a one-optional-parameter read-only listing tool with no output schema, the description carries the necessary information about what is returned and how to use it. The only real gap is not stating that the call returns all places when continent is omitted, and not clarifying the nesting when a country is requested by state name.

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 the single continent parameter (codes EU/NA/AS/OC/SA/AF or full name) is already fully documented in structured data. The description mentions 'continents' as a returned level but does not explain what omitting the parameter does or how the levels are nested, adding little meaning beyond the schema.

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 names the exact resource and its granularity: continents, countries, states, and cities that have upcoming quantum computing events, each with an event count. That level of specificity makes it clearly distinct from list_events, which consumes the same geography as a filter rather than producing it.

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?

It gives a concrete downstream usage rule: 'Use the codes or names it returns as filters for list_events,' which effectively positions this tool as the lookup step before event filtering. It stops short of an explicit 'use this when you need to narrow events by location, not when you already know the place,' leaving that inference to the agent.

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