Skip to main content
Glama
Sign In

Conference Partner

by com.myhuiban.www
OverviewDiscussionsAdmin

search_journals

Read-only

Search academic journals. Every parameter is optional — combine any of keyword, CCF rank, research field and ISSN. Returns a paginated list.

Input Schema

NameRequiredDescriptionDefault
issnNoISSN (fuzzy match)
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)
per_pageNoItems per page, max 100
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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)"
    • removedInput schema / properties / ccf_rank / enum
      Removed value: -[
-  "A",
-  "B",
-  "C"
-]
  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.5/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds that filters are optional and results are paginated, but it does not disclose sorting, result-field shape, or other behavioral details beyond what the schema and annotations provide.

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?

It is two compact sentences with no filler, and the core purpose is front-loaded. The optional-filter note and return note each contribute useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The schema fully documents seven parameters and the annotations establish read-only safety. However, with no output schema, the description only says 'paginated list' and does not explain result fields or ordering, leaving a gap for an agent trying to understand what comes back.

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?

The description names the main filter concepts (keyword, CCF rank, research field, ISSN), but omits page, per_page, and updated_since. With 100% schema description coverage, the schema already carries the detailed parameter semantics, so baseline 3 is appropriate.

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?

The description states a specific verb and resource: searching academic journals. It is clearly distinct from conference/researcher siblings by resource, but it does not explicitly differentiate itself from list_journals or get_journal.

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

Usage Guidelines3/5

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

It notes that all parameters are optional and filters can be combined, which implies how to use the tool. However, it does not say when to use search_journals instead of list_journals, get_journal, or search_conferences.

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