evipedia-mcp-dev 0.1.28 → 0.1.29
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/index.js +3 -3
- package/package.json +1 -1
package/dist/index.js
CHANGED
|
@@ -43,7 +43,7 @@ Typical workflow:
|
|
|
43
43
|
1. Discover \u2014 'search_reviews(query)' to find reviews matching an intervention name, synonym, drug class, or category; or 'list_reviews()' to enumerate/browse the entire catalogue as {topic, slug} pairs (topic = canonical topic; slug = the identifier you pass to get_review/get_conclusion, with the full review at https://evipedia.ai/{slug} and raw Markdown at https://evipedia.ai/{slug}.md). A bare topic implies the default Health & Longevity goal; an explicit goal like "Botox for Skin Rejuvenation" targets that goal.
|
|
44
44
|
2. Track changes \u2014 'list_updates(days?)' returns the catalogue's change feed, newest first: which reviews were newly published ('new') or revised ('updated') and when. Use it for recency questions ("what's new on evipedia?", "anything updated this week?"). With no arguments it covers the last 7 days (max 100 entries); pass 'days' for a wider window.
|
|
45
45
|
3. Read \u2014 take a review's slug and call 'get_conclusion(slug)' for the quick evidence-based bottom line, or 'get_review(slug)' for the complete review as Markdown (full methodology, findings, safety, dosing, and references) when the user wants depth or citations. Call 'get_metadata(slug)' for structured JSON metadata not in the Markdown \u2014 review dates (freshness), the typed intervention entity, and a machine-readable citation list with PubMed PMIDs.
|
|
46
|
-
4. Contribute \u2014 if the user wants an intervention reviewed that isn't in the catalogue, '
|
|
46
|
+
4. Contribute \u2014 if the user wants an intervention reviewed that isn't in the catalogue, 'suggest_review(...)' submits it to the evipedia team. Only call this when the user explicitly asks to propose one; it sends real data to the team.
|
|
47
47
|
|
|
48
48
|
'get_version()' reports the running build. Notes: an intervention may have multiple reviews for different goals (distinguished by canonical topic, e.g. "Botox for Skin Rejuvenation"). These are evidence reviews for information, not personalized medical advice \u2014 present conclusions as evidence summaries, not prescriptions.`;
|
|
49
49
|
var lunrCache = null;
|
|
@@ -193,8 +193,8 @@ Default window: the last ${window}${matched.length > list.length ? `, capped at
|
|
|
193
193
|
}
|
|
194
194
|
);
|
|
195
195
|
server2.tool(
|
|
196
|
-
"
|
|
197
|
-
"Suggest a new
|
|
196
|
+
"suggest_review",
|
|
197
|
+
"Suggest a new review for evipedia.ai \u2014 propose an intervention the catalogue doesn't cover yet. Submits to evipedia's public suggestion form (the same one at evipedia.ai/suggest). Use only when the user explicitly wants to propose a new review \u2014 this sends a message to the evipedia team.",
|
|
198
198
|
{
|
|
199
199
|
intervention: z.string().min(1).describe("Name of the intervention to suggest (e.g. 'Urolithin A')"),
|
|
200
200
|
goal: z.string().optional().describe("Optional health or longevity goal the intervention targets"),
|