Academic Writer MCP

Sources jamais citées

find_uncited_references

Read-onlyIdempotent

Identifies saved references that are not cited in any accepted project section, helping you spot missing citations before finalizing a bibliography.

Instructions

Sources enregistrées qui ne sont citées dans aucune section acceptée.

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": {
      "project_id": "<project_id>"
    },
    "name": "find_uncited_references"
  }
}

Input Schema

Name	Required	Description	Default
`project_id`	Yes

Output Schema

Name	Required	Description	Default
`count`	Yes
`sources`	Yes
`by_status`	Yes
`project_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 9, 2026

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 and openWorldHint=false, so the safety profile is covered. The description does add one non-obvious behavioral nuance: only citations inside *accepted* sections count, which materially affects what is returned and isn't derivable from 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 short clause with no filler, and the most important qualifier (accepted sections) is present. It is a noun phrase rather than a complete statement, so structure is terse to the point of being a fragment, 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?

An output schema exists, so return values need not be explained, and the tool is simple with one parameter. Still, for a lookup tool the description never states the project scoping rule or how an agent should act on the results, leaving modest gaps.

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

Parameters3/5

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

Only one parameter (project_id, required) exists, but schema description coverage is 0%, so nothing in structured data explains it. The description doesn't mention project scoping at all, leaving it ambiguous whether the search is project-wide or global; the baseline for a single trivial parameter keeps this at 3 rather than lower.

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 the resource (registered sources) and a precise filter condition (not cited in any accepted section), which is genuinely more specific than the name alone and separates it from list_sources or search_sources. It lacks a verb and doesn't name an explicit alternative, so it stops short of full sibling differentiation.

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 statement of prerequisites, and no mention of when a different sibling (e.g., audit_references or list_sources) would be the better choice. The intended usage is only implied by the filter condition itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server