ConferenceDB

Get a conference

get_conference

Read-onlyIdempotent

Use this when someone asks about one specific conference or trade show: when and where it is, who organizes it, what its sponsorship packages cost as the organizer publishes them, how many sponsors and exhibitors are listed, and which well-known companies are there. Takes the event name or its conferencedatabase.com slug.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name_or_slug": "<name_or_slug>"
    },
    "name": "get_conference"
  }
}

Input Schema

Name	Required	Description	Default
`name_or_slug`	Yes	A conference name such as "NAB Show" or "Money20/20", or its conferencedatabase.com slug such as "nab-show". A year in the name is ignored.

Output Schema

Name	Required	Description	Default
`found`	Yes
`message`	Yes
`conference`	Yes
`other_matches`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4.1/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 closed-world, so the safety profile is covered. The description adds genuinely useful behavioral context: sponsorship costs are returned 'as the organizer publishes them,' signaling possible gaps, plus what entity data accompanies the record. It doesn't discuss lookup failures or ambiguity handling, but adds real value over the 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?

Front-loads the trigger condition, then lists returned fields in one dense sentence. The field enumeration is long but each item is substantive; minor trimming of the list would sharpen it, but there is no filler.

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?

With an output schema present, return structure need not be explained, and annotations carry the safety profile. The description covers trigger, input form, and the notable caveat about organizer-published pricing, making it sufficiently complete for a single-parameter read tool.

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%, and the schema already explains the name/slug format and that a year in the name is ignored. The description restates 'takes the event name or its conferencedatabase.com slug' without adding syntax or edge-case detail beyond the schema, so baseline 3 applies.

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 ('get one specific conference or trade show') and enumerates the concrete facts returned (dates, location, organizer, sponsorship costs, sponsor/exhibitor counts, notable companies). This clearly distinguishes it from the discovery-oriented search_conferences sibling.

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?

Gives a clear trigger ('Use this when someone asks about one specific conference'), which implicitly routes discovery queries to search_conferences. It stops short of explicitly naming that alternative or stating when not to use this tool, so it's clear context without full exclusion guidance.

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

All ConferenceDB 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?