Skip to main content
Glama

QDev

List events

list_events
Read-onlyIdempotent

Upcoming quantum computing events, soonest first, as summaries. Every filter is optional and they combine. Events are run by their own organisers; QDev checks each against its organiser's page. At most 50 a call; pass nextCursor back as cursor for more.

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_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOnly events with a day on or before this date, YYYY-MM-DD.
tagNoA subject tag, such as quantum, research or industry.
cityNoA city name (Munich).
fromNoOnly events with a day on or after this date, YYYY-MM-DD.
kindNoThe kind of event.
textNoWords to look for in the title, summary, place, venue and tags. Every word must match.
limitNoHow many to return. 20 when left out.
cursorNoThe nextCursor of the previous call with the same filters.
formatNoHow the event is held.
regionNoA state or province, by ISO 3166-2 code (US-NV) or name (Nevada). Only some countries are searched by state.
countryNoAn ISO 3166-1 alpha-2 code (DE) or a country name (Germany).
continentNoA continent code (EU) or name (Europe).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds value beyond them: the 50-per-call cap, the pagination contract, and a provenance note that events are organiser-run and checked against the organiser's page. That provenance and limit information is exactly the kind of behavioral context annotations cannot express.

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?

Four compact sentences front-load the scope and ordering before moving to filter, provenance and pagination details; nothing is padded. It is dense but readable, with each clause carrying information an agent needs.

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 12-parameter, zero-required, read-only list tool with no output schema, the description covers ordering, filtering semantics, page size, pagination and data provenance. The only gap is what fields a 'summary' actually contains, a minor omission given the tool's simplicity.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds two things the schema does not: all filters are optional and they combine conjunctively, and the cursor must be replayed with the same filter set. For a 12-parameter tool, the AND-combination semantics materially reduce misuse.

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

Purpose4/5

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

The description names the resource (quantum computing events), the scope (upcoming, sorted soonest first) and the return granularity ('as summaries'), which implicitly distinguishes it from get_event's single-event detail. It stops short of naming that sibling outright, so differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

'Every filter is optional and they combine' plus the cursor-reuse rule ('pass nextCursor back as cursor for more') give real operational guidance for repeated calls. However, there is no explicit statement of when to reach for this tool versus get_event, search or list_places, so the when-to-use decision is only implied by the word 'Upcoming'.

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