Conference Partner

search_conferences

Read-only

Search academic conferences. Every parameter is optional — combine any of keyword, CCF/CORE/QUALIS rank, research field and submission/conference date ranges. Filter-only queries work fine (e.g. field=ai plus a submission-deadline window, no keyword). Returns a paginated list.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number, 1-based
`field`	No	Research field (e.g. ai, security, systems, ee, energy) - see the field enum for the full list
`query`	No	Keyword, matched against short/full name
`ccf_rank`	No	CCF rank
`per_page`	No	Items per page, max 100
`core_rank`	No	CORE rank
`qualis_rank`	No	QUALIS rank
`updated_since`	No	Incremental sync: only venues changed on/after this date (YYYY-MM-DD). Day granularity. Use the updated_at field of the results as your next checkpoint.
`conference_date_end`	No	Conference date until (YYYY-MM-DD)
`submission_date_end`	No	Submission deadline until (YYYY-MM-DD)
`conference_date_start`	No	Conference date from (YYYY-MM-DD)
`submission_date_start`	No	Submission deadline from (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 10, 2026

changedInput schema / properties / field / description

Previous value: -"Research field (one of 14 computer-science areas, e.g. ai, security, systems)"New value: +"Research field (e.g. ai, security, systems, ee, energy) - see the field enum for the full list"

changedInput schema / properties / field / enum

Previous value: -[
-  "ai",
-  "vision",
-  "nlp",
-  "data",
-  "network",
-  "security",
-  "se",
-  "systems",
-  "theory",
-  "hci",
-  "graphics",
-  "bio",
-  "robotics",
-  "web"
-]New value: +[
+  "ai",
+  "vision",
+  "nlp",
+  "data",
+  "network",
+  "security",
+  "se",
+  "systems",
+  "theory",
+  "hci",
+  "graphics",
+  "bio",
+  "robotics",
+  "web",
+  "ee",
+  "energy",
+  "materials",
+  "civil",
+  "education",
+  "management",
+  "math"
+]

Changed1 schema field changedAug 5, 2026

addedInput schema / properties / updated_since

Added value: +{
+  "description": "Incremental sync: only venues changed on/after this date (YYYY-MM-DD). Day granularity. Use the updated_at field of the results as your next checkpoint.",
+  "type": "string"
+}

Changed2 schema fields changedAug 5, 2026
- addedInput schema / properties / page / description
```
Added value: +"Page number, 1-based"
```
- addedInput schema / properties / per_page / description
```
Added value: +"Items per page, max 100"
```
Changed1 schema field changedAug 4, 2026
- removedInput schema / required
```
Removed value: -[
-  "query"
-]
```

Changed1 schema field changedJul 7, 2026

addedInput schema / properties / field

Added value: +{
+  "description": "Research field (one of 14 computer-science areas, e.g. ai, security, systems)",
+  "enum": [
+    "ai",
+    "vision",
+    "nlp",
+    "data",
+    "network",
+    "security",
+    "se",
+    "systems",
+    "theory",
+    "hci",
+    "graphics",
+    "bio",
+    "robotics",
+    "web"
+  ],
+  "type": "string"
+}

First observedJul 2, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description need not restate safety. It adds useful behavioral context: all parameters are optional, filter-only queries are valid, and the result is a paginated list. No contradiction with annotations.

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?

The description is three short sentences, front-loaded with the core purpose. Every sentence earns its place: first defines the tool, second explains parameter flexibility, third gives an example and return type. No redundancy or superfluous detail.

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 the tool has 12 optional parameters and no output schema, the description provides key context (search, filter combinations, paginated list) without over-explaining. It doesn't detail result fields or sorting, but those are not essential for selecting the tool, especially since sibling get_conference likely covers detail retrieval.

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 descriptions cover 100% of parameters, so baseline is 3. The description adds meaning by explaining that parameters can be combined arbitrarily and that filter-only queries (e.g., field plus submission_date window without keyword) are valid, which is not obvious from individual schema entries.

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 opens with 'Search academic conferences', which is a specific verb+resource. It clearly distinguishes from siblings like list_conferences (search vs. list) and search_journals (conferences vs. journals), and emphasizes the flexible filtering capabilities.

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 description provides clear context: every parameter is optional and can be combined, and filter-only queries are explicitly supported with a concrete example (field=ai plus submission-deadline window). It doesn't explicitly name alternatives or exclusions, but the search/filter nature is implicit from the sibling names.

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

All Conference Partner 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.

search_conferences

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources