Skip to main content
Glama
Sign In

Conference Partner

by com.myhuiban.www
OverviewDiscussionsAdmin

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

NameRequiredDescriptionDefault
pageNoPage number, 1-based
fieldNoResearch field (e.g. ai, security, systems, ee, energy) - see the field enum for the full list
queryNoKeyword, matched against short/full name
ccf_rankNoCCF rank: A, B or C. Comma-separate to match any of several (A,B,C = any CCF rank). Venues with no CCF rank have ccf_rank "" in the results
per_pageNoItems per page, max 100
core_rankNoICORE rank: A*, A, B or C. Comma-separate to match any of several (A*,A)
qualis_rankNoQUALIS rank: A1, A2, B1..B5. Comma-separate to match any of several (A1,A2)
updated_sinceNoIncremental 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_endNoConference date until (YYYY-MM-DD)
submission_date_endNoSubmission deadline until (YYYY-MM-DD)
conference_date_startNoConference date from (YYYY-MM-DD)
submission_date_startNoSubmission deadline from (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / ccf_rank / description
      Previous value: -"CCF rank"New value: +"CCF rank: A, B or C. Comma-separate to match any of several (A,B,C = any CCF rank). Venues with no CCF rank have ccf_rank \"\" in the results"
    • removedInput schema / properties / ccf_rank / enum
      Removed value: -[
-  "A",
-  "B",
-  "C"
-]
    • changedInput schema / properties / core_rank / description
      Previous value: -"CORE rank"New value: +"ICORE rank: A*, A, B or C. Comma-separate to match any of several (A*,A)"
    • removedInput schema / properties / core_rank / enum
      Removed value: -[
-  "A*",
-  "A",
-  "B",
-  "C"
-]
    • changedInput schema / properties / qualis_rank / description
      Previous value: -"QUALIS rank"New value: +"QUALIS rank: A1, A2, B1..B5. Comma-separate to match any of several (A1,A2)"
  2. Changed2 schema fields changed
    • 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"
+]
  3. Changed1 schema field changed
    • 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"
+}
  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. Changed1 schema field changed
    • removedInput schema / required
      Removed value: -[
-  "query"
-]
  6. Changed1 schema field changed
    • 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"
+}
  7. First observed

TDQS

A3.9/5.0
Behavior3/5

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

readOnlyHint already covers the safety profile, so the description's main contribution is 'Returns a paginated list', which tells the agent results are paged. It says nothing about default ordering, what happens with zero filters, or result size beyond the schema's per_page cap.

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?

Three short sentences, front-loaded with the action, then the combinability rule, then the return shape. Every sentence adds information; nothing is padded.

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 12 optional params and no output schema, the description gives the essentials an agent needs: filters compose, filter-only is valid, results are paginated. Missing details such as sort order or the behavior of an entirely unfiltered query are minor but real gaps.

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 baseline is 3, but the description adds cross-parameter semantics the schema can't: that keyword, CCF/CORE/QUALIS ranks, field, and both date ranges are all independently optional and combinable. Individual rank formats and date syntax are left to the schema, appropriately.

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?

States a specific verb and resource ('Search academic conferences') and the union of filterable facets. It doesn't explicitly contrast with list_conferences or search_journals, so an agent must infer that search = filtered retrieval while list = enumeration.

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?

Explains that every parameter is optional, that facets can be combined freely, and that filter-only queries are valid, with a concrete example (field=ai plus a submission-deadline window, no keyword). No exclusion rules or named alternatives, which keeps it short of a 5.

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