Skip to main content
Glama

Web citation access log

bpj_web_citation_access_log
Read-onlyIdempotent

Validate source URLs and calendar access dates and sort the resulting citation log chronologically.

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": {
      "records": "<records>"
    },
    "name": "bpj_web_citation_access_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that validation is performed and output is chronologically sorted, which is useful behavior beyond the annotations. It does not disclose what happens to malformed or unreachable URLs and dates, such as whether they are dropped, flagged, or cause an error, which matters most for a validation tool.

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 validation action and closed by the sorting outcome, with no padding. The chained 'and ... and ...' construction is slightly harder to parse than separate clauses but nothing is wasted.

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?

For a single-parameter, annotation-covered tool, this is close to adequate, but there is no output schema and the description does not say what the resulting citation log contains or how invalid entries are reported. That leaves the agent unable to predict the return value or failure mode.

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 one parameter at 0% schema description coverage, the description carries the burden. 'Validate source URLs and calendar access dates' tells the agent what content the records payload should contain, and 'one source per line' style input is implied by the singular records field. It stops short of restating the pipe-delimited Title|URL|access date format and the 3000-character limit that live only in the schema title.

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 names specific operations on specific resources: validating source URLs, validating calendar access dates, and sorting the citation log chronologically. It is far better than a tautology of the name. However, it does not differentiate itself from sibling citation tools such as bpj_citation_highwire_tags or bpj_dq_web_addresses, so an agent must infer the boundary.

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 explicit when-to-use guidance, no mention of when not to use it, and no named alternative. The only implicit cue is that it produces a chronological citation log, which suggests use during bibliography assembly, but choosing it over the sibling URL-validation or citation-parsing tools is left entirely to inference.

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.