Skip to main content
Glama

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

TableJSON 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
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 / 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"
+]
  2. 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"
+}
  3. 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"
  4. Changed1 schema field changed
    • removedInput schema / required
      Removed value: -[
-  "query"
-]
  5. 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"
+}
  6. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, covering the safety profile. The description adds that all parameters are optional and that the result is a paginated list, which is useful behavioral context. However, it does not clarify logical combination semantics (AND/OR) or behavior when no filters are applied.

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 two sentences, front-loaded with the primary purpose, and contains no filler or redundancy. Every sentence contributes to understanding the tool's functionality.

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?

For a 7-parameter search tool with no output schema, the description is minimal. It does not mention the updated_since parameter or the incremental sync use case, nor does it clarify the relationship with list_journals. The pagination detail is present, but overall the description leaves gaps in a broader context.

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%, with each parameter already well-documented. The description refers to 'keyword, CCF rank, research field and ISSN' but does not add significant meaning beyond the schema; 'keyword' also maps non-obviously to the 'query' parameter. This does not exceed the baseline of 3.

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 clearly states 'Search academic journals' with a specific verb and resource. It further explains that parameters can be combined and that results are paginated, making the tool's purpose unambiguous and distinct from sibling tools like list_journals and search_conferences.

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?

The description implies that the tool is for flexible, filtered searching with all parameters optional, which gives some usage context. However, it does not explicitly differentiate when to use this tool versus list_journals or get_journal, nor does it provide any exclusions or mention alternative tools.

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