Skip to main content
Glama

Conference Partner

by com.myhuiban.www
OverviewDiscussionsAdmin

list_journals

Read-only

Browse journal lists and rankings (special-issue CFPs, CCF, highest impact factor, popularity, all), paginated. No keyword filtering — use search_journals for that.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, 1-based
fieldNoResearch field filter. Only for ranking=cfp or ranking=all (e.g. ranking=cfp with field=network = network journals with an open special issue, soonest deadline first)
rankingYescfp=special-issue calls for papers; ccf=CCF list; highest_if=highest impact factor; most_viewed/most_tracked=popularity; all=all journals
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 or ranking=all (e.g. ranking=cfp with field=network = network journals with an open special issue, 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
    • addedInput schema / properties / page / description
      Added value: +"Page number, 1-based"
    • addedInput schema / properties / per_page / description
      Added value: +"Items per page, max 100"
  3. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the pagination trait, but says nothing about ordering within a ranking beyond what the enum implies, nor about response shape. Adequate but not rich.

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 sentences, zero filler, with the scope and the redirection front-loaded. Every clause earns its place.

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?

For a paginated read-only list tool with full schema descriptions and safety annotations, this is nearly sufficient. The only gap is that with no output schema, the agent gets no hint of what a journal entry contains, though that is minor for a browse tool.

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 coverage is 100% and each parameter, including the ranking and field enums, is fully documented in the schema itself. The description's parenthetical enumeration of ranking modes largely restates that. Baseline 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?

Specific verb ('Browse') plus resource ('journal lists and rankings') with the ranking modes enumerated (CFPs, CCF, impact factor, popularity, all). It explicitly distinguishes itself from the similarly-named sibling search_journals.

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?

States an explicit exclusion ('No keyword filtering') and routes the agent to the correct alternative ('use search_journals for that'). The condition that selects the sibling is unambiguous.

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