Skip to main content
Glama

CSL-JSON journal record

bpj_csl_journal_record
Read-onlyIdempotent

Encode structured authors, journal, volume and year as a CSL-JSON journal article record.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>",
      "authors": "<authors>",
      "year": "<year>",
      "journal": "<journal>",
      "volume": "<volume>"
    },
    "name": "bpj_csl_journal_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
titleYes
volumeYes
authorsYes
journalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is fully covered. The description adds nothing beyond that: it does not say what the emitted record looks like, whether the five inputs map one-to-one onto CSL fields, or what happens on invalid input. No contradiction with the annotations.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is also the source of the missing guidance.

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

Completeness2/5

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

With five required parameters, no output schema, and no annotations covering output shape, the description should at minimum sketch the resulting CSL-JSON structure or the author string convention. It does neither, leaving the agent to guess how the output is assembled.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameter burden, but it only echoes four of the five parameter names and omits title entirely. The critical format detail — authors are supplied one "family|given" name per line — appears only in the schema's property title, and the description neither restates nor clarifies it.

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 pairs a specific verb ("Encode") with a specific artifact ("CSL-JSON journal article record") and names the fields involved. It is clearly distinguishable from the sibling tools, which are generic JSON manipulation utilities, though it never explicitly contrasts itself with any of them.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The agent must infer that this is a citation-formatting helper rather than, say, a generic JSON emitter, purely from the resource noun.

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.