Academic Writer MCP

Lister les sources

list_sources

Read-onlyIdempotent

List a project's sources with verification status and citation counts to audit reference quality and spot unverified or mismatched entries. Filter by status to find sources needing review.

Instructions

Liste les sources du projet avec leur statut de vérification et leur nombre de citations.

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

Input Schema

Name	Required	Description	Default
`status`	No
`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/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is fully covered and the description needs only to add context. It does add that results include verification status and citation counts, which helps an agent interpret output. However, it discloses nothing about ordering, pagination or result limits.

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 compact sentence, front-loaded with the action and resource, with return fields appended. Nothing is wasted, though the brevity is what leaves filtering unaddressed.

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 needn't be explained, and mentioning status/citation counts is a small bonus. But with 0% parameter description coverage and no usage guidance, an agent is left guessing when to set status and why project_id is required.

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% for both parameters, so the description must compensate and largely fails. It gestures at verification status, but never clarifies that status is an optional filter over eight enumerated values, nor that project_id is the required scope. The schema carries the enum list; the description adds little meaning beyond 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 names a specific verb ("Liste") and resource ("les sources du projet") and says what each entry carries: verification status and citation count. That distinguishes it from search_sources as a plain enumeration, though the sibling is never named.

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: nothing explains why an agent would list sources here rather than search them via search_sources or pull documents via list_documents. It also doesn't mention that project_id is mandatory scoping or when the status filter should be applied.

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

Deploy Server