ConferenceDB

Get a conference's sponsors and exhibitors

get_conference_sponsors

Read-onlyIdempotent

Use this when someone asks which companies sponsor or exhibit at a specific conference. Returns company names, websites, role (sponsor, partner, media partner or exhibitor) and sponsorship level for one edition, ordered by how many conferences each company is listed at. Returns up to 50 companies per call with the total count; use offset to read further.

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

Input Schema

Name	Required	Description
`role`	No	Only companies with this role. Leave out for all roles.
`year`	No	Edition year. Leave out for the current or next edition.
`limit`	No	Companies to return, default 25, at most 50.
`offset`	No	Companies to skip, to read the next page.
`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
`offset`	Yes
`message`	Yes
`returned`	Yes
`companies`	Yes
`conference`	Yes
`role_counts`	Yes
`other_matches`	Yes
`total_matching`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4.5/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 useful context on ordering ('by how many conferences each company is listed at'), the 50-per-call cap and pagination via offset, though these overlap substantially with what the schema's limit/offset descriptions already say.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the usage trigger, then the return shape and pagination limit. Every clause carries information; nothing is repeated padding.

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?

For a single-resource lookup with full schema coverage, an output schema and rich annotations, the description supplies the trigger, result fields, ordering and pagination behavior. An agent has everything needed to call it correctly.

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 description coverage is 100%, so the baseline is 3; the enum values, year and name_or_slug are all documented in the schema itself. The description adds modestly by explaining the pagination intent ('use offset to read further') and tying the result set back to role ordering, which goes slightly beyond the field-level docs.

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 states a specific verb and resource (returns a conference's sponsors/exhibitors) and scopes it to one edition. It is readily distinguishable from get_company_conferences (the inverse lookup), get_conference (conference metadata) and search_conferences, even without naming them.

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?

The opening sentence gives a clear when-to-use trigger ('Use this when someone asks which companies sponsor or exhibit at a specific conference'). However, it never states when NOT to use it or names a sibling as the alternative, so routing against get_company_conferences is left to inference.

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?