viraldar

by ThomasRayvol

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Noter un post gardé

noter_post

Add or clear a takeaway note on a saved viral TikTok post, so you can record what to reuse when planning new content.

Instructions

Écrit (ou efface, avec une note vide) « ce que tu en reprends » sur un post déjà gardé dans À reproduire.

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": {
      "post": "<post>",
      "note": "<note>"
    },
    "name": "noter_post"
  }
}

Input Schema

Name	Required	Description	Default
`note`	Yes
`post`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does usefully disclose the destructive edge case that an empty note erases the existing value. It does not cover overwrite semantics, permissions, limits (2000 chars), or what is returned, which leaves meaningful gaps for a write tool.

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

Conciseness5/5

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

A single sentence with the main action front-loaded and the erase case handled in a compact parenthetical. Nothing is wasted and the conditional behavior sits right next to the verb it modifies.

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 two-parameter write tool with no annotations and no output schema, the description covers purpose, precondition, and the erase case. It still omits the post identifier format and any indication of the response, which an agent needs to call it confidently.

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?

Schema coverage is 0%, so the description must compensate for both parameters. It explains the meaning of 'note' well, including that empty input erases, and implies 'post' must reference an already-saved item, but it never specifies the post identifier format (id, slug, URL) nor the maxLength constraint.

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 ('Écrit') and a specific target ('sur un post déjà gardé dans À reproduire') plus the exact field being written ('ce que tu en reprends'), so the agent knows precisely what changes. It stops short of explicitly contrasting with the plain 'post' sibling, which is the main nearby ambiguity.

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

Usage Guidelines3/5

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

A precondition is stated clearly: the post must already be saved in 'À reproduire'. However, there is no guidance on when to use this versus 'post' or 'trier_post', and no statement of what happens if the post was never saved, so usage is only implied.

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