Skip to main content
Glama
Sign In

Conference Partner

by com.myhuiban.www
OverviewDiscussionsAdmin

list_conferences

Read-only

Browse conference lists and rankings (open CFPs, ranked venues with a call open now, popularity, most competitive, etc.), paginated. No keyword filtering — use search_conferences for that.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1-based
fieldNoResearch field filter. Only for ranking=cfp, past_cfp, upcoming, past or cp_index (e.g. ranking=cfp with field=ai = AI conferences still accepting papers, soonest deadline first)
rankingYescfp=open calls for papers; past_cfp=expired calls; ccf/core/qualis=venues in that tier whose submission deadline has not passed (for the whole tier catalogue use search_conferences with ccf_rank / core_rank / qualis_rank); cp_index=every conference ordered by the Conference Partner Index, our own 0-100 score - the only list here that covers the whole catalogue instead of the fifth of it that CCF / ICORE / QUALIS rate; each row carries cp_index with its confidence, and https://www.myhuiban.com/ranking has the method; most_viewed/most_tracked/most_attended=popularity; most_competitive=lowest acceptance rate; upcoming/past=by conference date; trending=most viewed in the last 30 days
per_pageNoItems per page, max 100

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / field
      Added value: +{
+  "description": "Research field filter. Only for ranking=cfp, past_cfp, upcoming, past or cp_index (e.g. ranking=cfp with field=ai = AI conferences still accepting papers, soonest deadline first)",
+  "enum": [
+    "ai",
+    "vision",
+    "nlp",
+    "data",
+    "network",
+    "security",
+    "se",
+    "systems",
+    "theory",
+    "hci",
+    "graphics",
+    "bio",
+    "robotics",
+    "web",
+    "ee",
+    "energy",
+    "materials",
+    "civil",
+    "education",
+    "management",
+    "math"
+  ],
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / ranking / description
      Previous value: -"cfp=open calls for papers; past_cfp=expired calls; ccf/core/qualis=venues in that tier whose submission deadline has not passed (for the whole tier catalogue use search_conferences with ccf_rank / core_rank / qualis_rank); most_viewed/most_tracked/most_attended=popularity; most_competitive=lowest acceptance rate; upcoming/past=by conference date; trending=most viewed in the last 30 days"New value: +"cfp=open calls for papers; past_cfp=expired calls; ccf/core/qualis=venues in that tier whose submission deadline has not passed (for the whole tier catalogue use search_conferences with ccf_rank / core_rank / qualis_rank); cp_index=every conference ordered by the Conference Partner Index, our own 0-100 score - the only list here that covers the whole catalogue instead of the fifth of it that CCF / ICORE / QUALIS rate; each row carries cp_index with its confidence, and https://www.myhuiban.com/ranking has the method; most_viewed/most_tracked/most_attended=popularity; most_competitive=lowest acceptance rate; upcoming/past=by conference date; trending=most viewed in the last 30 days"
    • changedInput schema / properties / ranking / enum
      Previous value: -[
-  "cfp",
-  "past_cfp",
-  "ccf",
-  "core",
-  "qualis",
-  "most_viewed",
-  "most_tracked",
-  "most_attended",
-  "most_competitive",
-  "upcoming",
-  "past",
-  "trending"
-]New value: +[
+  "cfp",
+  "past_cfp",
+  "ccf",
+  "core",
+  "qualis",
+  "most_viewed",
+  "most_tracked",
+  "most_attended",
+  "most_competitive",
+  "upcoming",
+  "past",
+  "trending",
+  "cp_index"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / ranking / description
      Previous value: -"cfp=open calls for papers; past_cfp=expired calls; ccf/core/qualis=tier lists; most_viewed/most_tracked/most_attended=popularity; most_competitive=lowest acceptance rate; upcoming/past=by conference date; trending=most viewed in the last 30 days"New value: +"cfp=open calls for papers; past_cfp=expired calls; ccf/core/qualis=venues in that tier whose submission deadline has not passed (for the whole tier catalogue use search_conferences with ccf_rank / core_rank / qualis_rank); most_viewed/most_tracked/most_attended=popularity; most_competitive=lowest acceptance rate; upcoming/past=by conference date; trending=most viewed in the last 30 days"
  4. Changed2 schema fields changed
    • addedInput schema / properties / page / description
      Added value: +"Page number, 1-based"
    • addedInput schema / properties / per_page / description
      Added value: +"Items per page, max 100"
  5. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark the tool read-only, and the description adds useful behavioral context: results are paginated, there is no keyword filtering, some rankings only cover rated venues, cp_index covers the whole catalogue, and each cp_index row carries confidence. These are substantive traits beyond the annotation.

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 tight sentences, front-loaded with the tool's purpose and immediately followed by the key exclusion and alternative. There is no wasted wording.

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 read-only, paginated list tool with no output schema and fully documented parameters, the description supplies the missing routing guidance and ranking coverage context. An agent has enough information to invoke it correctly and choose it over siblings.

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 documents page, field, ranking, and per_page in detail. The description reinforces the ranking categories but does not add syntax or constraints beyond what the schema provides, so the baseline of 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?

The description states a specific verb and resource: browsing conference lists and rankings, with examples of ranking types and pagination. It explicitly distinguishes this tool from search_conferences by noting the absence of keyword filtering.

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

Usage Guidelines5/5

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

It gives an explicit alternative: use search_conferences for keyword filtering. It also explains what the tool is for by naming ranking categories such as open CFPs, ranked venues with an open call, popularity, and most competitive.

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

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