Skip to main content
Glama

Check source

check_source
Destructive

Check a source of a project's register against the open services now: its arXiv id against arXiv, its DOI against Crossref, its zbMATH number against zbMATH Open — whether the work is there and whether its authors (by surname), title and year are the record's. Every service agreeing makes it 'api' (checked by a service) and takes the † off; a service disagreeing or not having the work makes it 'mismatch' with the reason field by field, with the †; a service that does not answer changes nothing and is said in 'silent'. A source a person checked against the original, or a mismatch a person set, keeps their word: what the services say otherwise comes back as 'serviceNote', without the †. 'newerVersion' says arXiv has a later version than the one checked. MR and ISBN are asked nowhere. Sources are also checked by themselves when an identifier is written and weekly, so call this only when the person wants it now; at most 30 a project an hour, answers kept a day per identifier. With 'all' and 'project' instead of one source: every source of the project the services have not vouched for — unchecked, or a mismatch the services set, never a person's word — that has an arXiv id, a DOI or a zbMATH number is put in the background check's queue and asked over the next minutes, outside the ration; the answer is 'queued' (how many wait), and list_sources' 'queued' and each source's 'services.queued' say what is still waiting — read them again later rather than calling this again. Members of the project who may write only.

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

Input Schema

NameRequiredDescriptionDefault
idNoThe source's id, as list_sources returned it.
allNotrue: queue every source of 'project' the services have not vouched for, instead of checking one now.
sourceNoIts key or an identifier it has, with 'project'.
projectNoThe project key, with 'source' — or with 'all'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / all
      Added value: +{
      +  "default": false,
      +  "description": "true: queue every source of 'project' the services have not vouched for, instead of checking one now.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / project / description
      Previous value: -"The project key, with 'source'."New value: +"The project key, with 'source' — or with 'all'."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already flag a non-read-only, destructive operation, and the description supports that by explaining status changes, removal of the dagger marker, mismatch reasons, silent services, service notes, newer-version detection, queue behavior, and rate limits. It also states the permission requirement that only project members who may write can use it.

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

Conciseness3/5

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

The content is largely purposeful and front-loads the core purpose, but it is delivered as one very dense paragraph with heavy semicolons and dashes. It is readable with effort, yet the structure could be much clearer for a tool this behaviorally complex.

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?

For a complex multi-service checker with no output schema, the description covers outcomes, side effects, permissions, rate limits, and queue follow-up well. Some domain-specific terms such as the dagger marker and the exact shape of 'serviceNote' are only partially explained, leaving a small completeness gap.

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?

Schema coverage is 100%, so the schema already documents all four parameters. The description still adds useful mode semantics, especially that pairing 'all' with 'project' queues eligible sources rather than checking one source immediately, and it explains the queued result and later inspection path.

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 states a specific verb and resource: checking a project register source against arXiv, Crossref, and zbMATH Open for presence and author/title/year agreement. It also clearly covers the batch queue mode, so an agent can distinguish this from get_source, list_sources, or set_source without opening the schema.

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

Usage Guidelines5/5

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

It explicitly says sources are checked automatically when identifiers are written and weekly, so this tool should be called only when the person wants a check now. It further explains the 'all' plus 'project' queue mode, the rate limit, and that queued results should be read later from list_sources rather than by calling again.

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