Skip to main content
Glama

Author-year citation disambiguation

bpj_author_year_disambiguation
Read-onlyIdempotent

Assign letter suffixes to works sharing an author and year, using title order within each group.

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": {
      "works": "<works>"
    },
    "name": "bpj_author_year_disambiguation"
  }
}

Input Schema

NameRequiredDescriptionDefault
worksYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description adds the ordering rule (title order) but says nothing about what the result looks like, how pre-existing suffixes in input titles are handled, or whether ordering is case-sensitive/locale-aware.

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?

One sentence, front-loaded with the action and followed by the tie-breaking rule; nothing is wasted. It is arguably too terse for the input-format ambiguity it leaves unresolved, but every word earns its place.

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?

A low-complexity, single-parameter tool with no output schema, so the description needn't explain return values in depth. However, for a tool whose whole job is producing a mapping of works to suffixes, omitting the shape of the result and the exact input encoding leaves a real gap for correct invocation.

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% and there is a single required parameter, so the description carries the burden of explaining input format. It alludes to authors, years and titles but never states the required 'Author|year|title, one work per line' structure, the 3000-char cap, or how duplicates are grouped — that only appears in the schema's title field. It adds some conceptual framing but does not compensate for the coverage gap.

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 and resource: 'assign letter suffixes to works sharing an author and year', plus the tie-breaking rule (title order within each group). An agent knows exactly what transformation happens; it just doesn't explicitly contrast with the citation siblings like bpj_citation_initials or bpj_ris_citation_import.

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 condition is implied by 'works sharing an author and year', so the agent can infer when disambiguation is needed, but there is no explicit when-to-use/when-not statement and no named alternative for callers who instead need citation formatting or import. Guidance is inferable rather than stated.

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.