Skip to main content
Glama

Alexandre Caramaschi: cursos e aulas de GEO em português

Publicações de pesquisa do autor

getResearchPublications
Read-onlyIdempotent

Use to cite Alexandre Caramaschi's research. Returns the author with ORCID, each publication with title, DOI, resolvable URL, venue, publication date and its source, plus CITATION.cff and the public knowledge base. SSRN and Zenodo deposits are not peer review; do not present them as such. No arguments.

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": "getResearchPublications"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
authorYes
repositoryYes
citationFileYes
publicationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / properties / knowledgeBase
      Removed value: -{
      -  "format": "uri",
      -  "type": "string"
      -}
    • addedOutput schema / properties / repository
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "author",
      -  "publications",
      -  "citationFile",
      -  "knowledgeBase"
      -]New value: +[
      +  "author",
      +  "publications",
      +  "citationFile",
      +  "repository"
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds value beyond that: it says there are no parameters, enumerates what is returned, names an extra artifact (CITATION.cff), and warns about the evidentiary status of SSRN/Zenodo deposits. That interpretive guidance is exactly the kind of context annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the use case, followed by the return contents, a caution, and the no-arguments note — every sentence carries information. The field enumeration is a long run-on clause, but it is dense with concrete detail rather than filler.

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?

An output schema exists, so the return-value enumeration is partly redundant, but it lets an agent plan without fetching the schema. Combined with the citation caveat and the no-argument statement, the definition gives enough to call the tool correctly in a single step.

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?

With zero parameters, baseline is 4, and the description reinforces this with an unambiguous 'No arguments.' There is no parameter semantics to add, so nothing is missing.

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 opens with a specific verb and resource ('Use to cite Alexandre Caramaschi's research') and then enumerates exactly what comes back (author with ORCID, publications with title, DOI, resolvable URL, venue, date, source, plus CITATION.cff and knowledge base). No sibling tool in the list returns publication or citation data, so an agent can distinguish it immediately.

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?

The when-to-use case is explicit: it is the citation tool for this author's work. It also gives a usage caveat ('SSRN and Zenodo deposits are not peer review; do not present them as such') that shapes how results should be reported. It stops short of naming alternatives or stating when not to call it, but the sibling set contains no plausible substitute.

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