Skip to main content
Glama

Fmind Freelance AI Architect Website

List publications

list_publications
Read-only

List academic and written publications: the PhD thesis, peer-reviewed papers, and hosted articles.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_publications"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
papersYes
thesisYes
articlesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / $defs / ArticleSummary / properties / canonical
      Removed value: -{
      -  "default": "",
      -  "title": "Canonical",
      -  "type": "string"
      -}
    • removedOutput schema / $defs / ArticleSummary / properties / syndicated
      Removed value: -{
      -  "default": "",
      -  "title": "Syndicated",
      -  "type": "string"
      -}
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered structurally. The description adds only the content taxonomy (thesis/papers/articles) and says nothing about ordering, completeness, or whether full text or just metadata is returned — a modest addition, not a rich one.

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?

A single front-loaded sentence naming the resource and its three content categories. Every clause earns its place and there is no filler or repetition of the title.

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 no parameters, a declared output schema, and read-only annotations, the description only needs to convey the scope of what is listed — which it does. Minor residual gap: it doesn't say whether the result is a complete enumeration or a summary view, which matters for a list-all tool.

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?

The tool takes zero parameters, so there is no parameter semantics to explain; the baseline for 0 params is 4. Nothing in the description misleads about inputs.

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 ('List') and resource ('academic and written publications'), and further enumerates the content types (PhD thesis, peer-reviewed papers, hosted articles). It is distinct from get_article in effect, though it never names that sibling to sharpen the contrast.

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?

Usage is only implied: an agent can infer this is the browse/all-publications call while get_article and search_articles handle single-item retrieval and searching. There is no explicit 'use this when…' or any stated exclusion against the siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources